C.P0087-0 E-UTRAN-HRPD Connectivity and Interworking - Air Interface Aspects v0.83 02apr2009 (Draft)

1
3GPP2 C.P0087-0
Version 0.83
Date: March 31, 2009
E-UTRAN cdma2000
Connectivity
Interworking: Air Interface Specification
and
Revision 0
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 Partners 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 Partners documents should be directed to
that Organizational Partner. See www.3gpp2.org for more information.
3GPP2 C.P0087-0 v0.83
Revision History
Version
Description of Changes
Date
v0.1
Initial Draft
3 December 2007
V0.11
Change table of content
25 August 2008
V0.1.4
All SWG22 approved contributions located under

Approved contributions in word folder
C22-20080929-005r1
C22-20080929-006r1
C23-20080930-005AMOT_IWK_Signaling_Link_Protocol.doc
C23-20080930-006AMOT_IWK_Signaling_Network_Protocol.doc
C23-20080930-007A-MOT_IWK_EnhancedMultiFlowPacketApplication.doc
C23-20080930-008AMOT_IWK_Session_Management_Protocol.doc
C23-20080930-009AMOT_IWK_Session_Configuration_Protocol.doc
C23-20080930-012r1_Qualcomm_QCeHRPD_EMPA-requirement.doc
1 October 2008
+
V0.1.5
C23-20080930-010r1-Motorola_LTE-HRPD1xalternate_EMPA.doc
C23-20080930-011r1MOT_IWK_Address_Management Protocol__IRMI.doc
C23-20080930-013A-C23-20080923008r1_IWK_SMP_KeepAlive_Stage3.doc
V0.1.6
Clean up reference and section numbers
V.0.1.7
C21-20080930-005R2
C21-20080930-006
Update to section 1
v.0.2.0
Baseline version
V0.5.0
Ballot version
1 October 2008
3GPP2 C.P0087-0 v0.83
No text.
ii
3GPP2 C.P0087-0 v0.83
CONTENTS
FOREWORD....................................................................................................................xli
REFERENCES................................................................................................................xlii
1 Overview.....................................................................................................................1-1
4
5
1.1 Introduction .........................................................................................................
1.2 Scope of This Document .......................................................................................
1.3 Requirement Language.........................................................................................
1.4 Architecture Reference Model................................................................................
1.5 Protocol Overview..................................................................................................
10
1.6 Terms...................................................................................................................
11
1.7 Notation................................................................................................................
2 Access terminal specific procedures............................................................................2-1
12
13
2.1 Access Terminal Bootup Procedure.......................................................................
14
2.2 E-UTRAN to HRPD Idle Handoff Procedure............................................................
15
2.3 Enhanced Multi-flow Packet Application Negotiation .............................................
16
2.4 Session Management Protocol Activation ..............................................................
3 Application Layer........................................................................................................3-1
17
18
3.1 Additional Requirement to support eHRPD operation ..........................................
4 Session Layer.............................................................................................................4-1
19
20
4.1 Default Session Management Protocol ...................................................................
21
4.1.1 Keep Alive Functions .......................................................................................
22
23
4.1.2 HRPD to E-UTRAN Idle Handoff Procedure and HRPD Prior Session
Handling ............................................................................................................
24
4.2 Default Address Management Protocol................................................................
25
4.2.1 Overview.......................................................................................................
26
4.2.2 Primitives and Public Data............................................................................
27
4.2.2.1 Commands..............................................................................................
28
4.2.2.2 Return Indications...................................................................................
29
4.2.2.3 Public Data.............................................................................................
30
4.2.3 UpdateUATI...................................................................................................
31
4.2.4 Setup State...................................................................................................
32
4.2.4.1 Access Terminal Requirements................................................................
iii
3GPP2 C.P0087-0 v0.83
4.2.4.2 Access Network Requirements.................................................................
4.2.5 Open State....................................................................................................
4.2.5.1 Access Terminal Requirements................................................................
4.2.5.2 Access Network Requirements.................................................................
4.2.6 Message Formats..........................................................................................
4.2.6.1 UATIAssignment......................................................................................
4.2.6.2 InterRATMobilityIndication ......................................................................
4.2.6.3 InterRATMobilityAck................................................................................
4.2.7 Indications....................................................................................................
10
4.2.8 Configuration Attributes...............................................................................
11
4.2.9 Protocol Numeric Constants..........................................................................
5 Connection Layer........................................................................................................5-1
12
13
5.1 Inter-RAT Signaling Adaptation Protocol ................................................................
14
5.1.1 Overview.........................................................................................................
15
5.1.2 Primitives and Public Data..............................................................................
16
5.1.2.1 Commands................................................................................................
17
5.1.2.2 Return Indications....................................................................................
18
5.1.2.3 Public Data...............................................................................................
19
5.1.3 Protocol Data Unit...........................................................................................
20
5.1.4 Protocol Initialization......................................................................................
21
5.1.4.1 Protocol Initialization for the InConfiguration Protocol Instance .................
22
5.1.4.2 Protocol Initialization for the InUse Protocol Instance ................................
24
5.1.5 Procedures and Messages for the InConfiguration Protocol Instance of the
Protocol..............................................................................................................
25
5.1.5.1 Procedures................................................................................................
26
5.1.5.2 Commit Procedures...................................................................................
27
5.1.5.3 Message Formats.......................................................................................
28
5.1.5.3.1 ConfigurationRequest..........................................................................
29
5.1.5.3.2 ConfigurationResponse ........................................................................
30
5.1.6 Procedures and Messages for the InUse Protocol Instance of the Protocol ........
31
5.1.6.1 Procedures................................................................................................
32
5.1.6.1.1 Command Processing..........................................................................
33
5.1.6.1.1.1 OpenConnection ............................................................................
23
iv
3GPP2 C.P0087-0 v0.83
5.1.6.1.1.2 CloseConnection ............................................................................
5.1.6.1.1.3 ActiveHandoffRequest....................................................................
5.1.6.1.1.4 IdleHandoffRequest........................................................................
5.1.6.1.2 Close State..........................................................................................
5.1.6.1.2.1 Access Terminal Requirements.......................................................
5.1.6.1.2.2 Access Network Requirements........................................................
5.1.6.1.3 Setup State..........................................................................................
5.1.6.1.3.2 Access Network Requirements......................................................
10
5.1.6.1.4 Open State.........................................................................................
12
5.1.6.1.5 Processing the

ReverseTrafficChannelMAC.OpenLoopParametersIssued indication .............
13
5.1.6.2 Message Formats.....................................................................................
14
5.1.6.2.1 AlternateLinkOpenReq.......................................................................
15
5.1.6.2.2 AlternateLinkOpenConf.....................................................................
16
5.1.6.2.3 AlternateLinkOpenFail.......................................................................
17
5.1.6.2.4 AlternateLinkCloseReq.......................................................................
18
5.1.6.2.5 AlternateLinkCloseConf.....................................................................
19
5.1.6.2.6 AlternateLinkPageReq........................................................................
20
5.1.6.2.7
11
AlternateLinkOpenComplete............................................................
21
5.1.6.3 Header Format........................................................................................
22
5.1.6.4 Interface to Other Protocols.....................................................................
23
5.1.6.4.1 Commands Sent................................................................................
24
5.1.6.4.2 Indications........................................................................................
25
26
27
5.1.9 Session State Information.............................................................................
28
5.2 Inter-RAT Initialization State Protocol..................................................................
29
5.2.1 Overview.......................................................................................................
30
31
5.2.2.1 Commands..............................................................................................
32
33
5.2.2.3 Public Data.............................................................................................
3GPP2 C.P0087-0 v0.83
5.2.3 Protocol Data Unit.........................................................................................
5.2.4 Protocol Initialization....................................................................................
5.2.4.1 Protocol Initialization for the InConfiguration Protocol Instance ...............
5.2.4.2 Protocol Initialization for the InUse Protocol Instance ..............................
5
6
5.2.5 Procedures and Messages for the InConfiguration Instance of the Protocol ........
23
5.2.5.1 Procedures..............................................................................................
5.2.5.2 Commit Procedures.................................................................................
5.2.5.3 Message Formats.....................................................................................
10
5.2.5.3.1 ConfigurationRequest........................................................................
11
5.2.5.3.2 ConfigurationResponse ......................................................................
12
5.2.6 Procedures and Messages for the InUse Instance of the Protocol ....................
13
5.2.6.1 Procedures..............................................................................................
14
5.2.6.1.1 Command Processing........................................................................
15
5.2.6.1.1.1 Activate........................................................................................
16
5.2.6.1.1.2 Deactivate....................................................................................
17
5.2.6.1.1.3 HRPDMeasStart...........................................................................
18
5.2.6.1.1.4 HRPDMeasStop............................................................................
19
5.2.6.1.2 Inactive State.....................................................................................
20
5.2.6.1.3 Network Determination State.............................................................
21
5.2.6.1.4 Pilot Acquisition State........................................................................
22
5.2.6.1.5 Synchronization State........................................................................
23
5.2.6.2 Message Formats.....................................................................................
24
5.2.6.2.1 Sync..................................................................................................
25
26
5.2.6.3.1 Commands Sent................................................................................
27
5.2.6.3.2 Indications........................................................................................
28
29
30
31
5.3 Inter-RAT Idle State Protocol................................................................................
32
5.3.1 Overview.......................................................................................................
33
vi
3GPP2 C.P0087-0 v0.83
5.3.2.1 Commands..............................................................................................
5.3.2.3 Public Data.............................................................................................
7
8
34
5.3.5.1 Procedures..............................................................................................
10
11
5.3.5.3 Message Formats.....................................................................................
12
13
14
15
5.3.6.1 Procedures..............................................................................................
16
17
5.3.6.1.1.1 Activate........................................................................................
18
5.3.6.1.1.2 Deactivate....................................................................................
19
5.3.6.1.1.3 OpenConnection ..........................................................................
20
5.3.6.1.1.4 Close...........................................................................................
22
5.3.6.1.2 Access Terminal Procedures for Sending a ConnectionRequest

Message......................................................................................................
23
5.3.6.1.3 T12 and T23 Computation....................................................................
24
5.3.6.1.4 Inactive State.....................................................................................
25
5.3.6.1.5 Sleep State........................................................................................
26
5.3.6.1.6 Monitor State.....................................................................................
27
5.3.6.1.6.1 Access Terminal Requirements.....................................................
28
5.3.6.1.6.1.1 CDMA Channel Selection .......................................................
29
5.3.6.1.6.1.2 Transition to Sleep State........................................................
30
31
5.3.6.1.6.2.1 General Requirements............................................................
32
5.3.6.1.7 Connection Setup State.....................................................................
33
21
vii
3GPP2 C.P0087-0 v0.83
5.3.6.1.8 Tunnel State......................................................................................
5.3.6.2 Message Formats.....................................................................................
5.3.6.2.1 Page...................................................................................................
5.3.6.2.2 ConnectionRequest............................................................................
5.3.6.2.3 ConnectionDeny ................................................................................
5.3.6.2.4 AttributeUpdateRequest.....................................................................
5.3.6.2.5 AttributeUpdateAccept.......................................................................
5.3.6.2.6 AttributeUpdateReject........................................................................
10
11
5.3.6.3.1 Commands Sent................................................................................
12
5.3.6.3.2 Indications........................................................................................
13
14
5.3.7.1 Simple Attributes....................................................................................
15
5.3.7.2 Complex Attributes..................................................................................
16
5.3.7.2.1 PreferredControlChannelCycle Attribute............................................
17
5.3.7.2.2 SlottedMode Attribute........................................................................
18
5.3.7.2.3 PagingMask Attribute........................................................................
19
20
21
5.4 Inter-RAT Route Update Protocol.........................................................................
22
5.4.1 Overview.......................................................................................................
23
24
5.4.2.1 Commands..............................................................................................
25
26
5.4.2.3 Public Data.............................................................................................
27
28
29
30
31
32
33
59
5.4.5.1 Procedures..............................................................................................
viii
3GPP2 C.P0087-0 v0.83
5.4.5.3 Message Formats.....................................................................................
5.4.6.1 Procedures..............................................................................................
5.4.6.1.1.1 Activate........................................................................................
5.4.6.1.1.2 Deactivate....................................................................................
10
5.4.6.1.1.3 Open............................................................................................
11
5.4.6.1.1.4 Close...........................................................................................
12
5.4.6.1.2 Pilots and Pilot Sets...........................................................................
13
5.4.6.1.2.1 Neighbor Set Search Window Parameters Update..........................
14
5.4.6.1.2.2 Pilot Search..................................................................................
15
5.4.6.1.2.3 Pilot Strength Measurement.........................................................
16
5.4.6.1.2.4 Pilot Drop Timer Maintenance......................................................
17
5.4.6.1.2.5 Active Set Management................................................................
18
5.4.6.1.2.6 Candidate Set Management..........................................................
19
5.4.6.1.2.7 Neighbor Set Management...........................................................
20
5.4.6.1.2.8 Remaining Set Management.........................................................
21
5.4.6.1.2.9 Pilot PN Phase Measurement........................................................
22
5.4.6.1.3 Message Sequence Numbers..............................................................
23
5.4.6.1.3.1 RouteUpdate Message Validation..................................................
24
5.4.6.1.3.2 TrafficChannelAssignment Message Validation .............................
25
5.4.6.1.3.3 AttributeOverride Message Validation ..........................................
26
5.4.6.1.4 Inactive State.....................................................................................
27
5.4.6.1.5 Idle State...........................................................................................
28
5.4.6.1.5.1 Active Set Maintenance................................................................
29
5.4.6.1.5.2 Pilot Channel Supervision in the Idle State..................................
31
5.4.6.1.5.3 Processing the TrafficChannelAssignment Message in the Idle

State........................................................................................................
32
5.4.6.1.5.4 Route Update Report Rules..........................................................
33
5.4.6.1.6 Connected State................................................................................
ix
30
3GPP2 C.P0087-0 v0.83
5.4.6.1.6.3.1 Access Network......................................................................
5.4.6.1.6.3.2 Access Terminal.....................................................................
5.4.6.1.6.4 ResetReport Message....................................................................
5.4.6.1.6.6 Processing the TrafficChannelAssignment Message in the

Connected State.......................................................................................
10
5.4.6.1.6.7 Processing the TrafficChannelComplete Message..........................
11
5.4.6.1.6.8 Transmission and Processing of the NeighborList Message ...........
13
5.4.6.1.6.9 Transmission and Processing of the AttributeOverride Message

................................................................................................................
14
5.4.6.1.6.10 Processing of OverheadMessages.Updated Indication .................
15
5.4.6.1.6.11 OverheadMessagesNeighborList Initialization .............................
16
5.4.6.1.7 Tunnel State .....................................................................................
17
5.4.6.1.7.1 Pilot Sets Maintenance.................................................................
18
5.4.6.1.7.1.1 Active Set Maintenance..........................................................
19
5.4.6.1.7.2 Pilot Channel Supervision in the Tunnel State.............................
12
21

Tunnel State............................................................................................
22
5.4.6.1.7.4 Route Update Report Rules in the Tunnel State............................
23
5.4.6.2 Message Formats.....................................................................................
24
5.4.6.2.1 RouteUpdate......................................................................................
25
5.4.6.2.2 TrafficChannelAssignment .................................................................
26
5.4.6.2.3 TrafficChannelComplete.....................................................................
27
5.4.6.2.4 ResetReport.......................................................................................
28
5.4.6.2.5 NeighborList......................................................................................
29
5.4.6.2.6 AttributeOverride...............................................................................
30
5.4.6.2.7 AttributeOverrideResponse ................................................................
31
5.4.6.2.8 RouteUpdateRequest..........................................................................
32
5.4.6.2.9 AttributeUpdateRequest...................................................................5-101
33
5.4.6.2.10 AttributeUpdateAccept...................................................................5-102
20
3GPP2 C.P0087-0 v0.83
5.4.6.2.11 AttributeUpdateReject....................................................................5-102
5.4.6.3 Interface to Other Protocols...................................................................5-103
5.4.6.3.1 Commands Sent..............................................................................5-103
5.4.6.3.2 Indications......................................................................................5-103
5.4.7 Configuration Attributes.............................................................................5-103
5.4.7.1 Simple Attributes...................................................................................5-103
5.4.7.2 Complex Attributes................................................................................5-106
5.4.7.2.1 SearchParameters Attribute.............................................................5-106
5.4.7.2.2 SetManagementSameChannelParameters Attribute..........................5-107
10
5.4.7.2.3 SetManagementDifferentChannelParameters Attribute.....................5-110
11
5.4.7.2.4 SupportedCDMAChannels Attribute................................................5-112
12
5.4.8 Protocol Numeric Constants........................................................................5-113
13
5.4.9 Session State Information...........................................................................5-114
14
5.4.9.1 RouteUpdate Parameter.........................................................................5-114
15
5.4.9.2 ExtendedRouteUpdate Parameter...........................................................5-116
16
5.4.9.3 AttributeOverrideMessageSequence Parameter......................................5-118
17
5.5 Inter-RAT Overhead Messages Protocol ..............................................................5-119
18
5.5.1 Overview.....................................................................................................5-119
19
5.5.2 Primitives and Public Data..........................................................................5-119
20
5.5.2.1 Commands............................................................................................5-119
21
5.5.2.2 Return Indications.................................................................................5-120
22
5.5.2.3 Public Data...........................................................................................5-120
23
5.5.3 Protocol Data Unit.......................................................................................5-120
24
5.5.4 Protocol Initialization..................................................................................5-120
25
5.5.4.1 Protocol Initialization for the InConfiguration Protocol Instance .............5-120
26
5.5.4.2 Protocol Initialization for the InUse Protocol Instance .............................5-121
27
28
121
29
5.5.5.1 Procedures............................................................................................5-121
30
5.5.5.2 Commit Procedures...............................................................................5-121
31
5.5.5.3 Message Formats...................................................................................5-122
32
5.5.5.3.1 ConfigurationRequest......................................................................5-122
33
5.5.5.3.2 ConfigurationResponse ....................................................................5-122
xi
3GPP2 C.P0087-0 v0.83
5.5.6 Procedures and Messages for the InUse Instance of the Protocol ..................5-123
5.5.6.1 Procedures............................................................................................5-123
5.5.6.1.1 Extensibility Requirements..............................................................5-123
5.5.6.1.2 Command Processing......................................................................5-123
5.5.6.1.2.1 Activate......................................................................................5-123
5.5.6.1.2.2 Deactivate..................................................................................5-123
5.5.6.1.2.3 TunnelDeactivate.......................................................................5-123
5.5.6.1.3 Inactive State...................................................................................5-124
5.5.6.1.4 Active State......................................................................................5-124
10
5.5.6.1.4.1 Access Network Requirements....................................................5-124
11
5.5.6.1.4.2 Access Terminal Requirements...................................................5-124
12
5.5.6.1.4.2.1 Supervision Procedures........................................................5-126
13
5.5.6.1.5 Tunnel Active State..........................................................................5-127
14
15
16
5.5.6.2 Message Formats...................................................................................5-128
17
5.5.6.2.1 QuickConfig....................................................................................5-128
18
5.5.6.2.2 SectorParameters.............................................................................5-130
19
5.5.6.2.3 HRPDSilenceParameters..................................................................5-139
20
21
5.5.6.3.1 Commands Sent..............................................................................5-140
22
5.5.6.3.2 Indications......................................................................................5-140
23
24
25
26
5.6 Default Signaling Adaptation Protocol ...............................................................5-142
27
5.6.1 Overview.....................................................................................................5-142
28
29
5.6.2.1 Commands............................................................................................5-142
30
31
5.6.2.3 Public Data...........................................................................................5-142
32
xii
3GPP2 C.P0087-0 v0.83
5.6.4.1 Protocol Initialization for the InConfiguration Instance of the Protocol .........
142
5.6.4.2 Protocol Initialization for the InUse Instance of the Protocol ...................5-142
5
6
143
5.6.5.1 Procedures............................................................................................5-143
5.6.5.3 Message Formats...................................................................................5-143
10
11
12
13
5.6.6.1 Procedures............................................................................................5-144
14
5.6.6.2 Message Formats...................................................................................5-144
15
16
5.6.6.3.1 Indications......................................................................................5-145
17
18
19
20
5.7 Default Air-Link Management Protocol ..............................................................5-146
21
5.7.1 Overview.....................................................................................................5-146
22
5.7.2 OpenConnection .........................................................................................5-148
23
5.7.3 CloseConnection .........................................................................................5-148
24
5.7.4 General Requirements for the Access Terminal in Idle State.........................5-149
25
5.7.5 General Requirements for the Access Network in Idle State..........................5-150
26
5.7.6 Commands Sent..........................................................................................5-150
27
5.8 Default Connected State Protocol......................................................................5-152
28
5.8.1 Inactive State..............................................................................................5-152
29
5.8.2 Indications..................................................................................................5-152
30
5.9 Default Packet Consolidation Protocol ...............................................................5-153
31
32
5.9.2 Access Terminal Requirement of Format A Packets.......................................5-154
33
5.9.3 Access Terminal Requirement of Format B Packets......................................5-154
xiii
3GPP2 C.P0087-0 v0.83
1
2
3
4
5
6
5.9.4 Access Network Requirement of Control Channel Connection Layer Packets

......................................................................................................................5-154
5.9.5 Access Network Requirement of Format A Packets of Forward Traffic
Channel.........................................................................................................5-155
5.9.6 Access Network Requirement of Format B Packets of Forward Traffic
Channel.........................................................................................................5-155
6 Initial Mean Output Power Requirement for Active Inter-RAT Handoff.........................6-1
7
8
6.1 Access Terminal Subtype 3 RTCMAC Protocol Requirement...................................
6.1.1 Return Indications..........................................................................................
10
6.1.2 Public Data.....................................................................................................
11
6.1.3 Inactive State..................................................................................................
12
6.1.4 Setup State.....................................................................................................
14
6.1.4.1 Access Terminal Requirements For Calculating Initial Mean Output

Power..............................................................................................................
15
6.1.5 Message Format..............................................................................................
16
6.1.5.1 HRPDOpenLoopParameters.......................................................................
17
6.2 Estimated Open-Loop Output Power.....................................................................
13
Annex A E-UTRAN-HRPD Call Flow Examples..................................................................A
18
xxxiixxxiii1-11-11-11-11-21-21-31-31-41-52-12-12-12-12-23-13-154-14-14-34-54-16420164-174-174-184-184-214-234-234-254-264-264-324-344-344-394-404-404-424-445-152115-15-25-25-35-35-35-35-35-45-45-45-45-55-55-55-65-65-65-65-75-75-75-75-75-85-952295-105-115-135-135-135-145-145-155-155-165-165-165-175-175-175-185-185-185-19523195-195-195-205-205-205-205-205-215-215-215-215-215-215-225-235-235-235-235-23524235-235-245-245-245-255-265-265-265-265-265-275-275-275-285-285-315-315-315-31525315-315-315-325-325-325-335-335-335-345-345-345-345-345-345-355-355-355-355-36526375-385-385-395-405-405-405-415-425-435-445-445-445-455-465-465-475-475-475-48527485-495-495-495-505-515-525-525-535-535-555-555-555-565-565-565-565-565-575-57528575-585-585-585-595-595-595-595-605-605-605-615-615-625-635-635-645-645-655-66529675-675-675-675-685-685-685-705-715-715-725-735-745-745-745-745-755-755-755-77530785-785-795-795-795-805-805-815-815-815-815-825-825-855-905-915-915-955-965-96531995-1005-1005-1015-1015-1015-1015-1025-1045-1045-1055-1085-1105-1115-1125321125-1145-1165-1175-1175-1175-1175-1185-1185-1185-1185-1185-1195-1195-1195331195-1205-1205-1205-1215-1215-1215-1215-1215-1215-1225-1225-1225-1225-1225341245-1255-1255-1255-1265-1265-1285-1385-1385-1385-1395-1395-1395-1405-1415351415-1415-1415-1415-1415-1415-1415-1415-1415-1425-1425-1425-1425-1425-1435361435-1435-1435-1445-1445-1445-1445-1445-1455-1455-1455-1465-1465-1475-1495371495-1495-1505-1505-1515-1515-1515-1525-1526-16-16-16-16-16-26-26-36-36-57381xxxiixxxiii1-11-11-11-11-21-31-41-52-12-12-12-12-23-13-154-14-14-34-54-164-16439174-174-184-184-194-194-194-204-204-204-214-224-224-234-234-234-254-264-264-32440344-394-404-404-414-445-15-15-15-25-25-35-35-35-35-35-45-45-45-45-55-55-55-65-6519
xiv
3GPP2 C.P0087-0 v0.83
65-65-75-75-75-75-75-85-95-95-105-115-135-135-135-145-145-155-155-165-165-1652175-175-175-185-185-185-195-195-195-195-205-205-205-205-205-215-215-215-215-2153215-225-235-235-235-235-235-235-235-245-245-245-255-265-265-265-265-265-275-2754275-285-285-315-315-315-315-315-315-315-325-325-325-335-335-335-345-345-345-3455345-345-355-355-355-355-365-375-385-385-395-405-405-405-415-425-435-445-445-4456455-465-465-475-475-475-485-485-495-495-495-505-515-525-525-535-535-555-555-5557565-565-565-565-565-575-575-575-585-585-585-595-595-595-595-605-605-605-615-6158625-635-635-645-645-655-665-675-675-675-675-685-685-685-705-715-715-725-735-7459745-745-745-755-755-755-775-785-785-795-795-795-805-805-815-815-815-815-825-82510855-905-915-915-955-965-965-995-1005-1005-1015-1015-1015-1015-1025-1045-1045111055-1085-1105-1115-1125-1125-1145-1165-1175-1175-1175-1175-1185-1185-1185121185-1185-1195-1195-1195-1195-1205-1205-1205-1215-1215-1215-1215-1215-1215131225-1225-1225-1225-1225-1245-1255-1255-1255-1265-1265-1285-1385-1385-1385141395-1395-1395-1405-1415-1415-1415-1415-1415-1415-1415-1415-1415-1415-1425151425-1425-1425-1425-1435-1435-1435-1435-1445-1445-1445-1445-1445-1455-1455161455-1465-1465-1475-1495-1495-1495-1505-1505-1515-1515-1515-1525-1526-16-161716-16-16-26-26-36-36-57-1Revision History.....................................................................i
1
REFERENCES................................................................................................................xxi
18
1 Overview.....................................................................................................................1-1
19
20
1.1 Introduction .........................................................................................................
21
1.2 Scope of This Document .......................................................................................
22
1.3 Requirement Language.........................................................................................
23
1.4 Architecture Reference Model................................................................................
24
1.5 Protocol Overview..................................................................................................
25
1.6 Terms...................................................................................................................
26
1.7 Notation................................................................................................................
2 Access terminal specific procedures............................................................................2-1
27
28
2.1 Access Terminal Bootup procedure.......................................................................
29
2.2 E-UTRAN to HRPD Idle Handoff Procedure............................................................
30
2.3 Enhanced Multi-flow Packet Application negotiation .............................................
31
2.4 Session Management Protocol activation ...............................................................
3 Signaling Application .................................................................................................3-1
32
33
3.1 Signaling Network Protocol....................................................................................
34
3.1.1 Procedures......................................................................................................
35
3.1.2 Type Definitions ..............................................................................................
36
3.1.3 Commands......................................................................................................
37
3.1.4 Indications......................................................................................................
xv
3GPP2 C.P0087-0 v0.83
3.2 Signaling Link Protocol.........................................................................................
3.2.1 Reset...............................................................................................................
3.2.2 Initialization for Reliable Delivery Procedures..................................................
3.2.3 Initialization for Fragmentation Layer Procedures............................................
3.2.4 Indications for Interface to Other Protocols ......................................................
3.3 Enhanced Multi-Flow Packet Application ..............................................................
7
8
3.3.1 Access Terminal Requirements of the InUse Instance of the Route Selection
Protocol..............................................................................................................
10
3.3.2 Indications for Interface to Other Protocols with the Route Selection
Protocol..............................................................................................................
11
3.3.3 Initialization and Reset for the InUse Instance of the Radio Link Protocol ........
12
3.3.4 Reset Procedure for the Initiating Side when it is an RLP Transmitter..............
13
3.3.5 Reset Procedure for Initiating Side when it is an RLP Receiver.........................
14
3.3.6 Reset Procedure for the Responding Side when it is an RLP Receiver...............
15
3.3.7 Reservation State Maintenance for RLP Transmit Procedures...........................
16
3.3.8 Access Terminal Requirements for Close State...............................................
17
3.3.9 Access Network Requirements for Close State................................................
18
3.3.10 Access Terminal Requirements for Open State.............................................
19
3.3.11 Access Network Requirements for Open State..............................................
20
3.3.12 Indications for Interface to Other Protocols with Radio Link Protocol ...........
21
3.4 Additional Requirement to support eHRPD operation ..........................................
4 Session Layer.............................................................................................................4-1
22
23
4.1 Default Session Management Protocol ...................................................................
24
4.1.1 Deactivate for the InUse Instance of the Protocol .............................................
25
4.1.2 Processing the SessionClose Message .............................................................
26
4.1.3 Processing Failed Indications ..........................................................................
27
4.1.4 Keep Alive Functions .......................................................................................
28
4.1.5 Close State......................................................................................................
29
4.1.6 Commands Sent.............................................................................................
30
4.2 Default Session Configuration Protocol .................................................................
31
4.2.1 Maintaining the ConnectionState Parameter....................................................
32
4.2.2 Maintaining the ConfigurationLock parameter................................................
33
4.2.3 Access Terminal Requirements of AN Initiated State........................................
xvi
3GPP2 C.P0087-0 v0.83
4.2.4 Access Network Requirements of AN Initiated State.........................................
4.2.5 Access Terminal Requirements of Open State................................................
4.2.6 Access Network Requirements of Open State.................................................
4.2.7 Commands....................................................................................................
4.2.8 Indications....................................................................................................
4.3 Inter-RAT Address Management Protocol.............................................................
4.3.1 Overview.......................................................................................................
4.3.2.1 Commands..............................................................................................
10
11
4.3.2.3 Public Data.............................................................................................
12
4.3.3 Connection Endpoints ..................................................................................
13
14
15
16
17
18
18
19
4.3.6.1 Procedures..............................................................................................
20
21
4.3.6.3 Message Formats.....................................................................................
22
23
24
25
4.3.7.1 Procedures..............................................................................................
26
27
4.3.7.1.1.1 Activate........................................................................................
28
4.3.7.1.1.2 Deactivate....................................................................................
29
4.3.7.1.1.3 UpdateUATI..................................................................................
30
4.3.7.1.2 UATIAssignment Message Validation ..................................................
31
4.3.7.1.3 Processing HardwareIDRequest message............................................
32
4.3.7.1.4 Inactive State.....................................................................................
33
xvii
3GPP2 C.P0087-0 v0.83
4.3.7.1.5 Setup State........................................................................................
4.3.7.1.6 Open State.........................................................................................
4.3.7.1.7 Processing of HRPD Information received via E-UTRAN......................
4.3.7.2 Message Formats.....................................................................................
10
4.3.7.2.1 UATIRequest......................................................................................
11
4.3.7.2.2 UATIAssignment................................................................................
12
4.3.7.2.3 UATIComplete....................................................................................
13
4.3.7.2.4 HardwareIDRequest...........................................................................
14
4.3.7.2.5 HardwareIDResponse.........................................................................
15
16
17
18
4.3.7.2.9 InterRATMobilityIndication ................................................................
19
4.3.7.2.10 InterRATMobilityAck........................................................................
20
21
4.3.7.3.1 Commands........................................................................................
22
4.3.7.3.2 Indications........................................................................................
23
4.3.7.4 Record Formats.......................................................................................
24
4.3.7.4.1 HRPDPreregistration..........................................................................
25
26
27
4.3.10 Session State Information...........................................................................
28
4.3.10.1 SessionSeed Parameter..........................................................................
29
4.3.10.2 MessageSequence Parameter.................................................................
30
4.3.10.3 HardwareID Parameter...........................................................................
5 Connection Layer........................................................................................................5-1
31
32
5.1 Inter-RAT Signaling Adaptation Protocol ................................................................
xviii
3GPP2 C.P0087-0 v0.83
5.1.1 Overview.........................................................................................................
5.1.2 Primitives and Public Data..............................................................................
5.1.2.1 Commands................................................................................................
5.1.2.2 Return Indications....................................................................................
5.1.2.3 Public Data...............................................................................................
5.1.3 Protocol Data Unit...........................................................................................
5.1.4 Protocol Initialization......................................................................................
5.1.4.1 Protocol Initialization for the InConfiguration Protocol Instance .................
5.1.4.2 Protocol Initialization for the InUse Protocol Instance ................................
11
5.1.5 Procedures and Messages for the InConfiguration Protocol Instance of the
Protocol..............................................................................................................
12
5.1.5.1 Procedures................................................................................................
13
5.1.5.2 Commit Procedures...................................................................................
14
5.1.5.3 Message Formats.......................................................................................
15
5.1.5.3.1 ConfigurationRequest..........................................................................
16
5.1.5.3.2 ConfigurationResponse ........................................................................
17
5.1.6 Procedures and Messages for the InUse Protocol Instance of the Protocol ........
18
5.1.6.1 Procedures................................................................................................
19
5.1.6.1.1 Command Processing..........................................................................
20
5.1.6.1.1.1 OpenConnection ............................................................................
21
5.1.6.1.1.2 CloseConnection ............................................................................
22
5.1.6.1.1.3 ActiveHandoffRequest....................................................................
23
5.1.6.1.1.4 IdleHandoffRequest........................................................................
24
5.1.6.1.2 Close State..........................................................................................
25
26
5.1.6.1.2.2 Access Network Requirements........................................................
27
5.1.6.1.3 Setup State..........................................................................................
28
29
30
5.1.6.1.4 Open State.........................................................................................
31
5.1.6.2 Message Formats.....................................................................................
32
5.1.6.2.1 AlternateLinkOpenReq.......................................................................
33
5.1.6.2.2 AlternateLinkOpenConf.....................................................................
xix
10
3GPP2 C.P0087-0 v0.83
5.1.6.2.3 AlternateLinkOpenFail.......................................................................
5.1.6.2.4 AlternateLinkCloseReq.......................................................................
5.1.6.2.5 AlternateLinkCloseConf.....................................................................
5.1.6.2.6 AlternateLinkPageReq........................................................................
5.1.6.3 Header Format........................................................................................
5.1.6.4.1 Commands Sent................................................................................
5.1.6.4.2 Indications........................................................................................
10
11
12
5.2 Inter-RAT Initialization State Protocol..................................................................
13
5.2.1 Overview.......................................................................................................
14
15
5.2.2.1 Commands..............................................................................................
16
17
5.2.2.3 Public Data.............................................................................................
18
19
20
21
22
23
19
24
5.2.5.1 Procedures..............................................................................................
25
26
5.2.5.3 Message Formats.....................................................................................
27
28
29
30
5.2.6.1 Procedures..............................................................................................
31
32
5.2.6.1.1.1 Activate........................................................................................
33
5.2.6.1.1.2 Deactivate....................................................................................
xx
3GPP2 C.P0087-0 v0.83
5.2.6.1.1.3 HRPDMeasStart...........................................................................
5.2.6.1.1.4 HRPDMeasStop............................................................................
5.2.6.1.2 Inactive State.....................................................................................
5.2.6.1.3 Network Determination State.............................................................
5.2.6.1.4 Pilot Acquisition State........................................................................
5.2.6.1.5 Synchronization State........................................................................
5.2.6.2 Message Formats.....................................................................................
5.2.6.2.1 Sync..................................................................................................
10
5.2.6.3.1 Commands Sent................................................................................
11
5.2.6.3.2 Indications........................................................................................
12
13
14
15
5.3 Inter-RAT Idle State Protocol................................................................................
16
5.3.1 Overview.......................................................................................................
17
18
5.3.2.1 Commands..............................................................................................
19
20
5.3.2.3 Public Data.............................................................................................
21
22
23
24
25
30
26
5.3.5.1 Procedures..............................................................................................
27
28
5.3.5.3 Message Formats.....................................................................................
29
30
31
32
5.3.6.1 Procedures..............................................................................................
33
xxi
3GPP2 C.P0087-0 v0.83
5.3.6.1.1.1 Activate........................................................................................
5.3.6.1.1.2 Deactivate....................................................................................
5.3.6.1.1.3 OpenConnection ..........................................................................
5.3.6.1.1.4 Close...........................................................................................
5.3.6.1.2 Access Terminal Procedures for Sending a ConnectionRequest

Message......................................................................................................
5.3.6.1.3 T12 and T23 Computation....................................................................
5.3.6.1.4 Inactive State.....................................................................................
5.3.6.1.5 Sleep State........................................................................................
10
5.3.6.1.6 Monitor State.....................................................................................
11
12
5.3.6.1.6.1.1 CDMA Channel Selection .......................................................
13
5.3.6.1.6.1.2 Transition to Sleep State........................................................
14
15
5.3.6.1.6.2.1 General Requirements............................................................
16
5.3.6.1.7 Connection Setup State.....................................................................
17
18
19
5.3.6.1.8 Tunnel State......................................................................................
20
5.3.6.2 Message Formats.....................................................................................
21
5.3.6.2.1 Page...................................................................................................
22
5.3.6.2.2 ConnectionRequest............................................................................
23
5.3.6.2.3 ConnectionDeny ................................................................................
24
25
26
27
28
5.3.6.3.1 Commands Sent................................................................................
29
5.3.6.3.2 Indications........................................................................................
30
31
32
33
5.3.7.2.1 PreferredControlChannelCycle Attribute............................................
xxii
3GPP2 C.P0087-0 v0.83
5.3.7.2.2 SlottedMode Attribute........................................................................
5.3.7.2.3 PagingMask Attribute........................................................................
5.4 Inter-RAT Route Update Protocol.........................................................................
5.4.1 Overview.......................................................................................................
5.4.2.1 Commands..............................................................................................
10
5.4.2.3 Public Data.............................................................................................
11
12
13
14
15
16
55
17
5.4.5.1 Procedures..............................................................................................
18
19
5.4.5.3 Message Formats.....................................................................................
20
21
22
23
5.4.6.1 Procedures..............................................................................................
24
25
5.4.6.1.1.1 Activate........................................................................................
26
5.4.6.1.1.2 Deactivate....................................................................................
27
5.4.6.1.1.3 Open............................................................................................
28
5.4.6.1.1.4 Close...........................................................................................
29
5.4.6.1.2 Pilots and Pilot Sets...........................................................................
30
5.4.6.1.2.1 Neighbor Set Search Window Parameters Update..........................
31
5.4.6.1.2.2 Pilot Search..................................................................................
32
5.4.6.1.2.3 Pilot Strength Measurement.........................................................
33
5.4.6.1.2.4 Pilot Drop Timer Maintenance......................................................
xxiii
3GPP2 C.P0087-0 v0.83
5.4.6.1.2.5 Active Set Management................................................................
5.4.6.1.2.6 Candidate Set Management..........................................................
5.4.6.1.2.7 Neighbor Set Management...........................................................
5.4.6.1.2.8 Remaining Set Management.........................................................
5.4.6.1.2.9 Pilot PN Phase Measurement........................................................
5.4.6.1.3 Message Sequence Numbers..............................................................
5.4.6.1.3.1 RouteUpdate Message Validation..................................................
5.4.6.1.3.2 TrafficChannelAssignment Message Validation .............................
5.4.6.1.3.3 AttributeOverride Message Validation ..........................................
10
5.4.6.1.4 Inactive State.....................................................................................
11
5.4.6.1.5 Idle State...........................................................................................
12
13
5.4.6.1.5.2 Pilot Channel Supervision in the Idle State..................................
15
5.4.6.1.5.3 Processing the TrafficChannelAssignment Message in the Idle

State........................................................................................................
16
17
5.4.6.1.6 Connected State................................................................................
18
19
20
21
5.4.6.1.6.3.1 Access Network......................................................................
22
5.4.6.1.6.3.2 Access Terminal.....................................................................
23
5.4.6.1.6.4 ResetReport Message....................................................................
24
14
26

Connected State.......................................................................................
27
5.4.6.1.6.7 Processing the TrafficChannelComplete Message..........................
28
5.4.6.1.6.8 Transmission and Processing of the NeighborList Message ...........
25
30

................................................................................................................
31
5.4.6.1.6.10 Processing of OverheadMessages.Updated Indication .................
32
5.4.6.1.6.11 OverheadMessagesNeighborList Initialization .............................
29
xxiv
3GPP2 C.P0087-0 v0.83
5.4.6.1.7 Tunnel State (editor: move this section after the Connected State
section).......................................................................................................
5.4.6.1.7.1 Pilot Set Maintenance..................................................................
5.4.6.1.7.2 Pilot Channel Supervision in the Tunnel State.............................

Tunnel State............................................................................................
5.4.6.1.7.4 Route Update Report Rules in the Tunnel State............................
5.4.6.2 Message Formats.....................................................................................
5.4.6.2.1 RouteUpdate......................................................................................
10
5.4.6.2.2 TrafficChannelAssignment .................................................................
11
5.4.6.2.3 TrafficChannelComplete.....................................................................
12
5.4.6.2.4 ResetReport.......................................................................................
13
5.4.6.2.5 NeighborList......................................................................................
14
5.4.6.2.6 AttributeOverride...............................................................................
15
5.4.6.2.7 AttributeOverrideResponse ................................................................
16
5.4.6.2.8 RouteUpdateRequest..........................................................................
17
18
5.4.6.2.10 AttributeUpdateAccept.....................................................................
19
5.4.6.2.11 AttributeUpdateReject......................................................................
20
21
5.4.6.3.1 Commands Sent................................................................................
22
5.4.6.3.2 Indications........................................................................................
23
24
25
26
5.4.7.2.1 SearchParameters Attribute...............................................................
27
5.4.7.2.2 SetManagementSameChannelParameters Attribute..........................5-100
28
5.4.7.2.3 SetManagementDifferentChannelParameters Attribute.....................5-103
29
5.4.7.2.4 SupportedCDMAChannels Attribute................................................5-105
30
31
32
5.4.9.1 RouteUpdate Parameter.........................................................................5-107
33
5.4.9.2 ExtendedRouteUpdate Parameter...........................................................5-109
xxv
3GPP2 C.P0087-0 v0.83
5.4.9.3 AttributeOverrideMessageSequence Parameter......................................5-111
5.5 Inter-RAT Overhead Messages Protocol ..............................................................5-112
5.5.1 Overview.....................................................................................................5-112
5.5.2.1 Commands............................................................................................5-112
5.5.2.3 Public Data...........................................................................................5-113
10
5.5.4.1 Protocol Initialization for the InConfiguration Protocol Instance .............5-113
11
5.5.4.2 Protocol Initialization for the InUse Protocol Instance .............................5-114
12
13
114
14
5.5.5.1 Procedures............................................................................................5-114
15
16
5.5.5.3 Message Formats...................................................................................5-115
17
18
19
20
5.5.6.1 Procedures............................................................................................5-116
21
5.5.6.1.1 Extensibility Requirements..............................................................5-116
22
5.5.6.1.2 Command Processing......................................................................5-116
23
5.5.6.1.2.1 Activate......................................................................................5-116
24
5.5.6.1.2.2 Deactivate..................................................................................5-116
25
5.5.6.1.2.3 TunnelDeactivate.......................................................................5-116
26
5.5.6.1.3 Inactive State...................................................................................5-117
27
5.5.6.1.4 Active State......................................................................................5-117
28
29
30
5.5.6.1.4.2.1 Supervision Procedures........................................................5-119
31
5.5.6.1.5 Tunnel Active State..........................................................................5-119
32
33
xxvi
3GPP2 C.P0087-0 v0.83
5.5.6.2 Message Formats...................................................................................5-121
5.5.6.2.1 QuickConfig....................................................................................5-121
5.5.6.2.2 SectorParameters.............................................................................5-123
5.5.6.2.3 HRPDSilenceParameters..................................................................5-133
5.5.6.3.1 Commands Sent..............................................................................5-133
5.5.6.3.2 Indications......................................................................................5-134
10
6 Initial Mean Output Power Requirement for Active Inter-RAT Handoff.........................6-1
11
12
6.1 Access Terminal Subtype 3 RTCMAC Protocol Requirement ..................................
13
6.1.1 Public Data.....................................................................................................
14
6.1.2 Inactive State..................................................................................................
15
6.1.3 Setup State.....................................................................................................
17
6.1.3.1 Access Terminal Requirements For Calculating Initial Mean Output

Power..............................................................................................................
18
6.1.4 Message Format..............................................................................................
19
6.1.4.1 HRPDOpenLoopParameters.......................................................................
20
6.2 Estimated Open-Loop Output Power.....................................................................
16
21
xxvii
3GPP2 C.P0087-0 v0.83
FIGURES
Figure 1.4-1. Architecture Reference Model ....................................................................
Figure 1.5-1. Non-Default Protocols ...............................................................................
Figure 3.1-1. ReservationLabel format.........................................................................5-21
Figure 4.2.1-1. Default Address Management Protocol State Diagram (Access

6
Terminal)................................................................................................................
5
Figure 4.2.1-2. Default Address Management Protocol State Diagram (Access

Network).................................................................................................................
7
8
Figure 5.2.1-1. Inter-RAT Initialization State Protocol State Diagram............................
Figure 5.3.1-1. Inter-RAT Idle State Protocol State Diagram (Access Terminal)..............
10
Figure 5.3.1-2. Inter-RAT Idle State Protocol State Diagram (Access Network)...............
11
Figure 5.3.6.1.7-1. Connection Setup Exchange ...........................................................
12
Figure 5.4.1-1. Inter-RAT Route Update Protocol State Diagram (Access Terminal) ........
13
Figure 5.4.1-2. Inter-RAT Route Update Protocol State Diagram (Access Network).........
14
Figure 5.4.6.1.5-1. Connection Setup Exchange for inter-RAT tunneling mode .............5-72
15
Figure 5.5.1-1. Inter-RAT Overhead Messages Protocol State Diagram........................5-119
16
Figure 5.7.1-1. Default Air Link Management Protocol State Diagram (Access
18
Terminal)..............................................................................................................5-146
17
Figure 5.7.1-2. Default Air Link Management Protocol State Diagram (Access
Network)...............................................................................................................5-147
19
20
Figure 5.9.1-1. Connection Layer Packet Structure (Format A)...................................5-153
21
Figure 5.9.1-2. Connection Layer Packet Structure (Format B)...................................5-153
22
Figure A-1 Access Terminal, UATI Assignment and Session Configuration over E24
UTRAN........................................................................................................................
23
Figure A-2 Access Network, UATI Assignment and Session Configuration over EUTRAN........................................................................................................................
25
26
Figure A-3 Access Terminal, E-UTRAN to HRPD Idle Handoff...........................................
27
Figure A-4 Access Network, E-UTRAN to HRPD Idle Handoff.............................................
28
Figure A-5 Access Terminal, E-UTRAN to HRPD Active Handoff........................................
29
Figure A-6 Access Network, E-UTRAN to HRPD Active Handoff.........................................
30
1-21-34-174-175-195-295-305-415-545-545-1177-27-37-47-57-67-7Figure 1.4-1.
32
Architecture Reference Model...................................................................................
31
Figure 1.5-1. Non-Default Protocols ...............................................................................
33
Figure 3.3.7-1. Reverse Link Reservation State Diagram (Access Terminal) ...................
34
xxviii
3GPP2 C.P0087-0 v0.83
Figure 3.3.7-2. Forward Link Reservation State Diagram (Access Network)...................
Figure 4.3.1-1. Inter-RAT Address Management Protocol State Diagram (Access

3
Terminal)................................................................................................................
2
Figure 4.3.1-2. Inter-RAT Address Management Protocol State Diagram (Access

Network).................................................................................................................
4
5
Figure 5.2.1-1. Inter-RAT Initialization State Protocol State Diagram............................
Figure 5.3.1-1. Inter-RAT Idle State Protocol State Diagram (Access Terminal)..............
Figure 5.3.1-2. Inter-RAT Idle State Protocol State Diagram (Access Network)...............
Figure 5.3.6.1.7-1. Connection Setup Exchange ...........................................................
Figure 5.4.1-1. Inter-RAT Route Update Protocol State Diagram (Access Terminal) ........
10
Figure 5.4.1-2. Inter-RAT Route Update Protocol State Diagram (Access Network).........
11
Figure 5.5.1-1. Inter-RAT Overhead Messages Protocol State Diagram........................5-112
12
13
xxix
3GPP2 C.P0087-0 v0.83
TABLES
Table 2.1-1. Bootup Protocol Type and Protocol Subtype in E-UTRAN............................
Table 4.2.8-1. Configurable Values..............................................................................4-43
Table 5.1.6.2-1. Encoding of the RequestReason Field..................................................
Table 5.3.6.1.5-1. Computation of Periodi from SlotCyclei............................................
Table 5.3.6.2.2-1. Encoding of the RequestReason Field...............................................
Table 5.3.6.2.3-1. Encoding of the DenyReason Field...................................................5-48
Table 5.3.7.1-1Configurable Simple Attributes.............................................................
Table 5.3.7.2.3.3-1. Definition of MaskPurpose Field of a Paging Mask........................
Table 5.4.1-1. Route Update Protocol Parameters that are Public Data of the Overhead
11
Messages Protocol..................................................................................................
10
Figure 5.4.1-2. Inter-RAT Route Update Protocol State Diagram (Access Network).........5-56
12
Table 5.4.6.2-1. DRCLength Encoding .........................................................................
13
Table 5.4.6.2-2. Encoding of the RABLength Field.......................................................
14
Table 5.4.6.2-3. Reverse Activity Channel Gain Encoding .............................................
15
Table 5.4.6.2-4. Search Window Sizes..........................................................................
16
Table 5.4.6.2-5. Search Window Offset.........................................................................
17
Table 5.4.6.2.8-1. Search Window Sizes.......................................................................
18
Table 5.4.6.2.8-2. Search Window Offset....................................................................5-100
19
Table 5.4.7.1-1. Configurable Values ..........................................................................5-104
20
Table 5.4.7.2.2-1. Pilot Drop Timer Values.................................................................5-108
21
Table 5.4.9.1-1. The Format of the Parameter Record for the RouteUpdate Parameter
............................................................................................................................5-113
22
23
Table 5.4.9.2-1. The Format of the Parameter Record for the ExtendedRouteUpdate
25
Parameter.............................................................................................................5-116
24
Table 5.4.9.3-1. The Format of the Parameter Record for the

AttributeOverrideMessageSequence Parameter..........................................................5-118
26
27
Table 5.5.6.2-1. Search Window Sizes........................................................................5-134
28
Table 5.5.6.2-2. Search Window Offset.......................................................................5-135
29
Table 5.5.7-1 Configurable Simple Attributes.............................................................5-140
30
Table 5.7.1-1. Active Protocols Per Air Link Management Protocol State.....................5-146
31
Table 5.7.1-2. Active Protocols Per Air Link Management Protocol State when access
33
terminal TunnelModeEnabled is equal to 1.........................................................5-146
32
xxx
3GPP2 C.P0087-0 v0.83
2
terminal TunnelModeEnabled is equal to 0.........................................................5-146
1
Table 6.1.5-1PilotStrengthNominal Encoding .................................................................
Table 6.1.5-2PilotStrengthCorrectionMin Encoding ........................................................
Table 6.1.5-3. PilotStrengthCorrectionMax Encoding .....................................................
Table 6.2-1. Relative Power Levels vs. Data Rate for Access Channel Transmissions .........
7
7
8
2-1
4-435-145-375-45
10
5-465-495-525-555-875-885-895-935-945-985-995-1035-1075-1125-115
11
5-1165-1335-1345-1396-46-46-56-7Table 2.1-1. Bootup Protocol Type and Protocol

13
Subtype in E-UTRAN...............................................................................................
12
Table 3.1.2-1. Default Protocol Stack Type Values..........................................................
14
Table 4.3.7.2-1. HardwareIDType encoding ..................................................................
15
Table 4.3.10.1-1. The Format of the Parameter Record for the SessionSeed Parameter
..............................................................................................................................
16
17
Table 4.3.10.2-2. The Format of the Parameter Record for the MessageSequence
19
Parameter...............................................................................................................
18
Table 4.3.10.3-3. The Format of the Parameter Record for the HardwareID Parameter
..............................................................................................................................
20
21
Table 5.1.6.2-1. Encoding of the RequestReason Field..................................................
22
Table 5.3.6.1.5-1. Computation of Periodi from SlotCyclei............................................
23
Table 5.3.6.2.2-1. Encoding of the RequestReason Field...............................................
24
Table 5.3.7.1-1Configurable Simple Attributes.............................................................
25
Table 5.3.7.2.3-1. Definition of MaskPurpose Field of a Paging Mask...........................
26
28
Messages Protocol..................................................................................................
27
Table 5.4.6.2-1. DRCLength Encoding .........................................................................
29
Table 5.4.6.2-2. Encoding of the RABLength Field.......................................................
30
Table 5.4.6.2-3. Reverse Activity Channel Gain Encoding .............................................
31
Table 5.4.6.2-4. Search Window Sizes..........................................................................
32
Table 5.4.6.2-5. Search Window Offset.........................................................................
33
Table 5.4.6.2.8-1. Search Window Sizes.......................................................................
34
xxxi
3GPP2 C.P0087-0 v0.83
Table 5.4.6.2.8-2. Search Window Offset......................................................................
Table 5.4.7.1-1. Configurable Values ............................................................................
Table 5.4.7.2.2-1. Pilot Drop Timer Values.................................................................5-102
5
............................................................................................................................5-107
4
Parameter.............................................................................................................5-110
6
7
Table 5.5.6.2-1. Search Window Sizes........................................................................5-128
Table 5.5.6.2-2. Search Window Offset.......................................................................5-129
Table 5.5.7-1 Configurable Simple Attributes.............................................................5-134
10
Table 6.1.4-1PilotStrengthNominal Encoding .................................................................
11
Table 6.1.4-2PilotStrengthCorrectionMin Encoding ........................................................
12
Table 6.1.4-3. PilotStrengthCorrectionMax Encoding .....................................................
13
Table 6.2-1. Relative Power Levels vs. Data Rate for Access Channel Transmissions .........
15
7
14
16
xxxii
3GPP2 C.P0087-0 v0.83
FOREWORD
(This foreword is not part of this standard)
This standard was prepared by Technical Specification Group C of the Third Generation
4Partnership Project 2 (3GPP2). This standard is evolved from and is a companion to the
1
5cdma2000
standards. This standard contains the air interface requirements for facilitating
6High Rate Packet Data (HRPD) interworking with the Evolved Universal Terrestrial Radio
7Access Network (E-UTRAN).
This specification applies to High Rate Packet Data Release
8Revision A compliant access terminals and access networks which are enhanced to support
9the E-UTRAN and HRPD interworking.
3
This is a supplementary specification to HRPD air interface specifications.
10
This standard consists of the following sections:
11
12
1.
General. This section defines the acronyms and terms used in this document.
13
2.
cdma2000 HRPD interworking with E-UTRAN. This section specifies the required
HRPD procedures and messages for HRPD interworking with E-UTRAN.
14
1 cdma2000 is the trademark for the technical nomenclature for certain specifications and standards
3of
the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication),
4cdma2000
5United
is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the
States.
xxxiii
3GPP2 C.P0087-0 v0.83
REFERENCES
The following standards contain provisions which, through reference in this text, constitute
provisions of this standard. At the time of publication, the editions indicated were valid. All
4standards are subject to revision, and parties to agreements based on this standard are
5encouraged to investigate the possibility of applying the most recent editions of the
6standards indicated below.
2
3
7
8
[1]
3GPP2 C.S0024-A v3.0: cdma2000 High Rate Packet Data Air Interface Specification.
[2]
3GPP2 C.S0024-0 v4.0: cdma2000 High Rate Packet Data Air Interface Specification.
10
[3]
3GPP2 C.S0063-A v2.0: cdma2000 High Rate Packet Data Supplemental Services.
11
[4]
3GPP2 C.R1001-G: Administration of Parameter Value Assignments for cdma2000 Spread

Spectrum Standards
13
[5]
3GPP2 X.S0057: E-UTRAN-eHRPD Connectivity and Interworking: Core Network Aspects
14
[6]
3GPP2 A.S0022: Interoperability Specification (IOS) for Evolved High Rate Packet Data
(eHRPD) Radio Access Network Interfaces and Interworking with Enhanced Universal
Terrestrial Radio Access Network (E-UTRAN)
17
[7]
3GPP TS 23.402: Architecture Enhancements for non-3GPP accesses.
18
[8]
3GPP2 X.S0011-001 cdma2000 Wireless IP Network Standard: Introduction
19
[9]
C.S0005: Upper Layer (Layer3) SingalingSignaling Specification for cdma2000 Spread

Spectrum Systems
12
15
16
20
21
22
23
[10] ITU-T Recommendation E.212: Identification Plan for Land Mobile Stations, 1988
[11] 3GPP TS36.331 Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource
Control (RRC) Protocol specification
24
25
xxxiv
3GPP2 C.P0087-0 v0.83
1 OVERVIEW
1.1 Introduction
These technical requirements form a compatibility standard for facilitating cdma2000 High
4Rate Packet Data (HRPD) interworking with the Evolved Universal Terrestrial Radio Access
5Network (E-UTRAN). This technical specification also forms requirements on the air-interface
6to support Evolved High Rate Packet Data (eHRPD).
3
This is a supplementary specification built on top of the existing cdma2000 High Rate Packet
Data (HRPD) air interface specifications. All requirements of the existing 3GPP2 C.S0024-A
9v3.0 [1], 3GPP2 C.S0063-A v2.0 [3] are included and assumed by this specification, unless
10explicitly excluded or modified herein.
7
8
The concept of handoff with optimization between E-UTRAN and cdma2000 is specified in
123GPP TS 23.402 [7]
11
1.2 Scope of This Document
13
This specification applies to High Rate Packet Data Release Revision A compliant access
15terminals and access networks which are enhanced to support the E-UTRAN and HRPD
16interworking.
14
These requirements ensure that a compliant access terminal can obtain interworking service
18through any access network conforming to this standard. These requirements do not address
19the quality or reliability of that service, nor do they cover equipment performance or
20measurement procedures.
17
This specification is primarily oriented toward requirements necessary for the design and
implementation of access terminals. As a result, detailed procedures are specified for access
23terminals to ensure a uniform response to all access networks. Access network procedures,
24however, are specified only to the extent necessary for compatibility with those specified for the
25access terminal.
21
22
This specification includes provisions for future service additions and expansion of system
capabilities. The architecture defined by this specification permits such expansion without the
28loss of backward compatibility to older access terminals.
26
27
1.3 Requirement Language
29
Compatibility, as used in connection with this standard, is understood to mean: Any access
terminal can obtain service through any access network conforming to this standard.
32Conversely, all access networks conforming to this standard can service access terminals.
30
31
Shall and shall not identify requirements to be followed strictly to conform to the standard
and from which no deviation is permitted. Should and should not indicate that one of
35several possibilities is recommended as particularly suitable, without mentioning or excluding
36others, that a certain course of action is preferred but not necessarily required, or that (in the
37negative form) a certain possibility or course of action is discouraged but not prohibited. May
33
34
3GPP2 C.P0087-0 v0.83
and need not indicate a course of action permissible within the limits of the standard. Can
2and cannot are used for statements of possibility and capability, whether material, physical,
3or causal.
1
1.4 Architecture Reference Model
The architecture reference model for inter-radio-access technoloytechnology interworking, more

6specifically cdma2000 (HRPD ) interworking with E-UTRAN, is presented in Figure 1.4 -1. The
7reference model consists of the following functional units: the cdma2000 mode of the dual
8mode access terminals, the cdma2000 access network and the Tunnel.
5
9
10
Figure 1.4-1. Architecture Reference Model
The cdma2000 mode of the dual mode access terminals and the cdma2000 access network are
defined in section 1.6. The Tunnel involves the dual mode access terminals, air interface and
13access network associated with the other radio access technology, as well as the core networks.
14The elements related to the tunnel interface shown in Figure 1.4 -1 are specified in [11], [5],
15[6] and [11][6]].
11
12
The reference model includes the cdma2000 air interface between the dual mode access
terminal and the cdma2000 access network, the tunnel interface between the Tunnel and the
18cdma2000 mode of the dual mode access terminal, and the tunnel interface between the
19Tunnel and the cdma2000 access network.
16
17
The cdma2000 inter-radio-access-technology interworking protocols used over the tunnel

21interfaces and the cdma2000 air interface are defined in this document.
20
22
3GPP2 C.P0087-0 v0.83
1.5 Protocol Overview
This specification defines additional procedures and requirements on the following protocols in
[1].
2
3
Default Session Management Protocol
Default Address Management Protocol
Default Air-Link Management Protocol
Default Connected State Protocol
Default Packet Consolidation Protocol
Subtype 3 Reverse Traffic Channel MAC Protocol
10
Subtype 2 Physical Layer Protocol
Additionally, this specification defines a new protocol in Connection Layer called Signaling
12Adaptation Protocol. Default Signaling Adaptation Protocol and Inter-RAT Signaling Adaptation
13Protocol subtypes of the protocol are also defined in this specification.
11
Figure 1.6.6-1 of [1] presents default protocols defined for each one of the layers shown in
15Figure 1.4.1-1 of [1].
Figure 1.5-1 presents the non-default protocols defined in this
16specification for each one of the layers show in Figure 1.4.1-1 of [1].
14
3GPP2 C.P0087-0 v0.83
Application
Layer
Stream
Layer
Session
Layer
Inter-RAT
Initialization
State Protocol
Inter-RAT
Idle State
Protocol
Inter-RAT
Route Update
Protocol
Inter-RAT
Overhead
Messages
Protocol
Inter-RAT
Signaling
Adaptation
Protocol
Connection
Layer
Security
Layer
MAC
Layer
Physical
Layer
1
2
Figure 1.5-2. Non-Default Protocols
3
4
5
1.6 Terms
Access Network (AN). The network equipment providing data connectivity between a packet
switched data network (typically the Internet) and the access terminals. An access network is
9equivalent to a base station in [1].
7
8
3GPP2 C.P0087-0 v0.83
Access Terminal (AT). A device providing data connectivity to a user. An access terminal may
2be connected to a computing device such as a laptop personal computer or it may be a self3contained data device such as a personal digital assistant. An access terminal is equivalent to
4a mobile station in [1].
1
CDMA2000 Mode of Dual Mode Access Terminal. An operation mode of a dual mode access
terminal which provides the connectivity over the cdma2000 HRPD air interface. A dual mode
7access terminal may operate in the cdma2000 mode or the mode of another radio access
8technology such as E-UTRAN.
5
6
Code Division Multiple Access (CDMA). A technique for spread-spectrum multiple-access

10digital communications that creates channels through the use of unique code sequences.
9
eHRPD. Refer [5] for eHRPD definition.
11
E-UTRAN. Evolved Universal Terrestrial Radio Access Network.
12
HSGW. HRPD Serving Gateway.
13
HRPDPreRegistrationZoneID. An identifier broadcasted by E-UTRAN cells associated with a

15neighboring HRPD subnet. This identifier is similar set to the value of ColorCode in usageof
16the access network associated with the E-UTRAN cells.
14
HRPDSecondaryPreRegZoneID. An identifier broadcasted by E-UTRAN cells associated with a

18neighboring HRPD subnet. This identifier is set to the value of ColorCode of a neighboring AN
19associated with the E-UTRAN cellssimilar to SecondaryColorCode in usage.
17
MAC Layer. The MAC Layer defines the procedures used to receive and to transmit over the
21Physical Layer. The MAC Layer is defined in Chapter 10 of [1].
20
NULL. A value which is not in the specified range of the field.
22
PDN. Packet Data Network.
23
Primary Radio Access Technology. The Radio Access Technology on which the access
terminal can transmit at the present time.
24
25
PreRegistrationZone. The
27HRPDPreRegistrationZoneID.
26
group
of
E-UTRAN
cells
which
broadcast
the
same
Reverse Traffic Channel. The portion of the Reverse Channel that carries information from a
specific access terminal to the access network. The Reverse Traffic Channel can be used as
30either a Dedicated Resource or a non-Dedicated Resource. Prior to successful access terminal
31authentication, the Reverse Traffic Channel serves as a non-Dedicated Resource. Only after
32successful access terminal authentication can the Reverse Traffic Channel be used as a
33Dedicated Resource for the specific access terminal.
28
29
RLP. Radio Link Protocol provides retransmission and duplicate detection for an octet-aligned
35data stream.
34
36
3GPP2 C.P0087-0 v0.83
1.7 Notation
A[i]
The ith element of array A. The first element of the array is A[0].
<e1, e2, , en>
3
4
5
6
7
structure
with
elements
e1,
e2,
en.
Two structures E = <e 1, e2, , en> and F = <f1, f2, , fm> are equal if and
only if m is equal to n and ei is equal to fi for i=1, n.
Given E = <e1, e2, , en> and F = <f1, f2, , fm>, the assignment E = F
denotes the following set of assignments: ei = fi, for i=1, n.
S.e
The member of the structure S that is identified by e.
M[i:j]
Bits ith through jth inclusive (i j) of the binary representation of variable

M. M[0:0] denotes the least significant bit of M.
9
10
11
12
Concatenation operator. (A | B) denotes variable A concatenated with

variable B.
Indicates multiplication.
Indicates the largest integer less than or equal to x: 1.1 = 1, 1.0 = 1.
Indicates the smallest integer greater or equal to x: 1.1 = 2, 2.0 = 2.
|x|
Indicates the absolute value of x: |17|=17, |17|=17.
Indicates exclusive OR (modulo-2 addition).
Indicates bitwise logical AND operator.
min (x, y)
Indicates the minimum of x and y.
max (x, y)
Indicates the maximum of x and y.
x mod y
Indicates the remainder after dividing x by y: x mod y = x (y x/y ).
x^y
Indicates the result of x raised to the power y, also denoted as x y.
xy
Indicates the result of x raised to the power y, also denoted as x^y.
13
14
15
16
17
18
19
20
21
22
23
Unless otherwise specified, the format of field values is unsigned binary.
24
Unless indicated otherwise, this standard presents numbers in decimal form. Binary numbers
are distinguished in the text by the use of single quotation marks. Hexadecimal numbers are
27distinguished by the prefix 0x.
25
26
Unless specified otherwise, each field of a packet shall be transmitted in sequence such that
the most significant bit (MSB) is transmitted first and the least significant bit (LSB) is
30transmitted last. The MSB is the left-most bit in the figures in this document. If there are
28
29
3GPP2 C.P0087-0 v0.83
multiple rows in a table, the top-most row is transmitted first. If a table is used to show the
2sub-fields of a particular field or variable, the top-most row consists of the MSBs of the field.
3Within a row in a table, the left-most bit is transmitted first. Notations of the form repetition
4factor of N or repeated N times mean that a total of N versions of the item are used.
1
3GPP2 C.P0087-0 v0.83
2 ACCESS TERMINAL SPECIFIC PROCEDURES
The procedures defined in this section describe general requirements to which access
terminals and access networks shall comply with in order to enable E-UTRANHRPD
4interworking.
2
3
2.1 Access Terminal Bootup Procedure
When the HRPD protocol stack is created, if the primary radio-access-technology is not
7HRPDE-UTRAN, then the access terminal shall create an InUse instance of each of the Protocol
8Typeprotocol types listed in Table 2.1-1, using the respective protocol subtype. For Protocols
9Typeprotocol types not listed in Table 2.1-1, the access terminal shall create the InUse protocol
10instance using the dDefault pProtocol sSubtypes. When the HRPD protocol stack is created, if
11the primary radio-access-technology is not HRPD, the access terminal shall create the InUse
12instance of Inter-RAT Signaling Adaptation Protocol, and then create the InUse instances of
13other protocols.
6
14
Table 2.1-1. Bootup Protocol Type and Protocol Subtype in E-UTRAN
15
Protocol Type
Name
Protocol Subtype
ID
Name
ID
Initialization State
0x0b
Inter-RAT Initialization State
0x0001
Idle State
0x0c
Inter-RAT Idle State
0x0003
Route Update
0x0e
Inter-RAT Route Update
0x0002
Overhead Messages
0x0f
Inter-RAT Overhead Messages
0x0001
Address Management
0x11
Inter-RAT Address Management
0x0001
Signaling Adaptation
Reverse Traffic
ChannelMAC
0x1d
Inter-RAT Signaling Adaptation

Subtype 3 Reverse Traffic
ChannelMAC
0x0001
0x04
0x0003
16
2.2 E-UTRAN to HRPD Idle Handoff Procedure
17
Upon the access terminal performing an E-UTRAN to HRPD idle handoff, if the Protocol
19Subtypeprotocol subtype of the Signaling Adaptation protocol is equal to 0x0000 [4] or if there
20is no InUse instance of the Signaling Adaptation Protocol, then the access terminal shall issue
21an AirLinkManagement.OpenConnection command. Otherwise the access terminal shall issue a
22SignalingAdaptation.IdleHandoffRequest command.
18
2.3 Enhanced Multi-flow Packet Application Negotiation
23
If the access terminal requires eHRPD service using Enhanced Multi-flow Packet Application,
25the access terminal shall include both the Enhanced Multi-Flow Packet Application subtype
24
3GPP2 C.P0087-0 v0.83
(0x0009) and alternate Enhanced Multi-Flow Packet Application 2 subtype (0xFFFE) in the
2ATSupportedApplicationSubtypes
attribute during session negotiation of the Session
3Configuration Protocol. The alternate EMPA subtype shall not be bound to any stream. During
4Stream Protocol negotiation, the access terminal shall propose the Enhanced Multi-Flow
5Packet Application subtype (0x0009) and shall not propose the alternate EMPA subtype
6(0xFFFE).
1
2.4 Session Management Protocol Activation
The access terminal shall not perform preregistration or session maintenance of HRPD session
via E-UTRAN if the primary radio-access-technology is E-UTRAN and the E-UTRAN protocol
3
10within the access terminal has disabled preregistration .
8
9
11
12
13
14
The specification C.R1001 defines an alternate Enhanced Multi-Flow Packet Application subtype in
3addition
4Flow
5as
to the existing Enhanced Multi-Flow Packet Application subtype. The alternate Enhanced Multi-
Packet Application subtype (0xFFFE) is only reported during SCP negotiation and is not proposed
an application subtype during Stream Protocol configuration.
3 HRPD session negotiation between the access terminal and the access network by other means than
7via
HRPD radio access technology..
3GPP2 C.P0087-0 v0.83
3 APPLICATION LAYER
3.1 Signaling Network Protocol
3.1.1 Procedures
This section supersedes 2.5.4.1 of [1].
SNP receives messages for transmission from multiple protocols. SNP shall add the SNP header
to each message and forward it for transmission to SLP.
5
6
SNP receives messages from SLP. SNP shall route these messages to their associated protocols
8according to the value of the InConfigurationProtocol and Type field in the SNP header. If
9InConfigurationProtocol field in the SNP header is set to 1, the SNP shall route the message to
10the InConfiguration instance of the protocol identified by the Type field, otherwise the SNP
11shall route the message to the InUse instance of the protocol identified by the Type field.
7
If an SNP message is to be transmitted on the Forward Traffic Channel or on the Reverse

13Traffic
Channel,
and if a connection
is
not
open, SNP
shall
issue
a
14SignalingAdaptation.OpenConnection command, if the Protocol Subtype of the Signaling
15Adaptation
Protocol is not equal to 0x0000, otherwise SNP shall issue an
16AirlinkManagement.OpenConnection command. SNP should queue all messages requiring
17transmission in the Forward Traffic Channel or in the Reverse Traffic Channel until the
18protocol receives a SignalingAdaptation.ConnectionOpened indication, if the Protocol Subtype of
19the Signaling Adaptation Protocol is not equal to 0x0000, otherwise until the protocol receives
20an IdleState.ConnectionOpened indication.
12
When SNP receives an SLP.Reset indication, it shall refrain from passing messages from
22protocols other than SLP for transmission to SLP until it receives an SLP.ResetAcked
23indication.
21
3.1.2 Type Definitions
24
25
Type definitions associated with the default protocol stack are presented in Table 3.1.2-1. The
constant name and protocol layer are provided for informational purposes.
26
27
3GPP2 C.P0087-0 v0.83
Table 3.1.2-2. Default Protocol Stack Type Values
3GPP2 C.P0087-0 v0.83
Type
Protocol
Constant
Name
Layer
0x14
Stream 0 Application
NAPP0Type
Application
0x15
NAPP1Type
Application
0x16
NAPP2Type
Application
0x17
NAPP3Type
Application
0x13
Stream Protocol
NSTRType
Stream
0x19
Virtual Stream
NVSPType
Stream
0x10
Session Management Protocol
NSMPType
Session
0x11
Address Management Protocol
NADMPType
Session
0x12
Session Configuration
Protocol
NSCPType
Session
0x1b
Multimode Capability
Discovery
NMCDType
Session
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
0x1d
Signaling Adaptation Protocol
NSAPType
Connection
0x08
Security Protocol
NSPType
Security
0x05
Key Exchange Protocol
NKEPType
Security
0x06
Authentication Protocol
NAPType
Security
0x07
Encryption Protocol
NEPType
Security
0x01
Control Channel MAC

Protocol
NCCMPType
MAC
0x02
Access Channel MAC Protocol
NACMPType
MAC
0x03
Forward Traffic Channel MAC

Protocol
NFTCMPType
MAC
0x04
Reverse Traffic Channel MAC

Protocol
NRTCMPType
MAC
3GPP2 C.P0087-0 v0.83
Type
0x00
Protocol
Constant
Name
Physical Layer Protocol
NPHYPType
3.1.3 Commands
This section supersedes 2.5.4.5.1 of [1].
This protocol issues the following commands:
AirLinkManagement.OpenConnection
SignalingAdaptation.OpenConnection
3.1.4 Indications
This protocol registers to receive the following indications:
IdleState.ConnectionOpened
10
SignalingAdaptation.ConnectionOpened
11
SLP.Reset
12
SLP.ResetAcked
13
Layer
Physical
3GPP2 C.P0087-0 v0.83
3.2 Signaling Link Protocol
3.2.1 Reset
SLP can only be reset at the initiative of the access network. To reset SLP, the access network
6shall perform the following:
5
The access network shall initialize its data structures as described in 3.2.3 and 3.2.2,
The access network shall return a Reset indication, and
The access network shall send a Reset message.
Upon receiving a Reset message, the access terminal shall validate the message sequence
number as defined 14.6 in [1]. If the message is valid, the access terminal shall respond with a
12ResetAck message and shall initialize its data structures as described in 3.2.3 and 3.2.2. If the
13message sequence number of the Reset message is not valid, the access terminal shall discard
14the message.
10
11
The SLP in the access network shall return a ResetAcked indication when it receives a
ResetAck message with a MessageSequence field equal to the MessageSequence sent in the
17Reset message. If the Protocol Subtype of the Signaling Adaptation Protocol is not equal to
180x0000, after reception of a SignalingAdaptation.ConnectionInitiated indication, the access
19network shall set the MessageSequence sent in the first Reset message to one. Otherwise after
20the protocol receives a RouteUpdate.ConnectionInitiated indication, the access network shall set
21the MessageSequence sent in the first Reset message to one. The access network shall
22increment the sequence number for every subsequent Reset message it sends.
15
16
The access terminal shall initialize the reset receive pointer used to validate Reset messages
24(see 14.6 in [1]) to 0 when the protocol receives a SignalingAdaptation.ConnectionInitiated
25indication, if the Protocol Subtype of the Signaling Adaptation Protocol is not equal to 0x0000,
26otherwise when the protocol receives a RouteUpdate.ConnectionInitiated indication.
23
3.2.2 Initialization for Reliable Delivery Procedures
27
This section supersedes section 2.6.4.2.3.2 of [1].
28
When SLP-D is initialized or reset it shall perform the following:
29
30
Set the send state variable V(S) to zero in the transmitter.
31
Set the receive state variable V(N) to zero in the receiver.
32
Set Rx[i] to 0 for i = 0...2S-1.
33
Clear the retransmission and resequencing buffers.
34
Discard any SLP-D packets queued for retransmission.
When SLP-D is initialized or is reset, the sender shall begin sending SLP-D packets with an
36initial SequenceNumber of 0.
35
3GPP2 C.P0087-0 v0.83
The access terminal and the access network shall perform the initialization procedure,
If the Protocol Subtype of the Signaling Adaptation Protocol is not equal to 0x0000, and the
protocol receives a SignalingAdaptation.ConnectionInitiated indication,
Otherwise, if the protocol receives a RouteUpdate.ConnectionInitiated indication.
3.2.3 Initialization for Fragmentation Layer Procedures
This section supersedes section 2.6.4.3.2 of [1].
When SLP-F is initialized or reset it shall perform the following:
Set the send state variable V(S) to zero in the transmitter.
Set Sync to zero.
10
Clear the re-assembly buffers.
When SLP-F is initialized or reset, the sender shall begin sending SLP-F packets with an initial
12SequenceNumber of 0.
11
The access terminal and the access network shall perform the initialization procedure,
13
15
If the Protocol Subtype of the Signaling Adaptation Protocol is not equal to 0x0000 and the
protocol receives a SignalingAdaptation.LinkAcquired indication,
16
Otherwise, if the protocol receives a ReverseTrafficChannelMAC.LinkAcquired indication.
14
3.2.4 Indications for Interface to Other Protocols
17
This section supersedes section 2.6.7.2 of [1].
18
19
20
RouteUpdate.ConnectionInitiated
21
ReverseTrafficChannelMAC.LinkAcquired
22
ControlChannelMAC.Interrupted
23
SignalingAdaptation.ConnectionInitiated
24
SignalingAdaptation.LinkAcquired
25
3GPP2 C.P0087-0 v0.83
3.3 Enhanced Multi-Flow Packet Application
3.3.1 Access Terminal Requirements of the InUse Instance of the Route Selection Protocol
The Route Selection Protocol associated with an activated Link Flow can be in one of four
states: A Open B Setting, A Open B Rising, A Setting B Open, or A Rising B Open. The Route
7Selection Protocol instance associated with all activated Link Flows shall be in the same state
8at any time. When a Link Flow is activated, the Route Selection Protocol shall enter the state
9that the Route Selection Protocols of other activated Link Flows are in. If no other Link Flows
10are activated when a Link Flow is activated, then the Route Selection Protocol shall enter the A
11Open B Setting state. If the Route Selection Protocol receives a
5
6
14
SignalingAdaptation.ConnectionClosed indication, if the Protocol Subtype of the Signaling

Adaptation Protocol is not equal to 0x0000, otherwise if the protocol receives a
ConnectedState.ConnectionClosed indication or
15
RouteUpdate.ConnectionLost indication,
12
13
it shall enter the A Open B Setting state. Figure 2.4.4.1.2-1 on [3]], shows the state diagram for
the Route Selection Protocol at the access terminal.
16
17
3.3.2 Indications for Interface to Other Protocols with the Route Selection Protocol
18
19
20
21
ConnectedState.ConnectionClosed
22
SignalingAdaptation.ConnectionClosed
23
RouteUpdate.ConnectionLost
3.3.3 Initialization and Reset for the InUse Instance of the Radio Link Protocol
24
This section supersedes section 2.5.4.1.1 of [3]
25
The RLP initialization procedure initializes the RLP variables and data structures in one end of
27the link. The RLP reset procedure guarantees that RLP state variables on both sides are
28synchronized. The reset procedure includes initialization.
26
The access terminal and the access network shall perform the initialization procedures defined
30in 2.5.4.1.1.1.1 and 2.5.4.1.1.1.2 of [1] for both routes of all activated Link Flows if the protocol
31receives a:
29
33
SignalingAdaptation.ConnectionOpened indication, if the Protocol Subtype of the Signaling

Adaptation Protocol is not equal to 0x0000,
34
Otherwise, if the protocol receives an IdleState.ConnectionOpened indication.
32
3GPP2 C.P0087-0 v0.83
The access network shall perform the initialization procedure defined in 2.5.4.1.1.1.1 of [1] for
2both routes of forward Link Flow NN when forward Link Flow NN is activated. The access
3terminal shall perform the initialization procedure defined in 2.5.4.1.1.1.2 of [1] for both routes
4of forward Link Flow NN when forward Link Flow NN is activated. The access terminal shall
5perform the initialization procedure defined in 2.5.4.1.1.1.1 of [3] for both routes of reverse
6Link Flow NN when reverse Link Flow NN is activated. The access network shall perform the
7initialization procedure defined in 2.5.4.1.1.1.2 of [3] for both routes of reverse Link Flow NN
8when reverse Link Flow NN is activated. Upon receiving an InitializeRoute command, the access
9terminal shall perform the initialization procedures defined in 2.5.4.1.1.1.1 of [3] for the
10specified Route of all activated Link Flows. Upon receiving an InitializeRoute command, the
11access network shall perform the initialization procedures defined in 2.5.4.1.1.1 of [3] for the
12specified Route of all activated Link Flows.
1
3.3.4 Reset Procedure for the Initiating Side when it is an RLP Transmitter
13
This section supersedes section 2.5.4.1.1.2.1 of [3].
14
If the side initiating a reset procedure is an RLP transmitter for the Route of the Link Flow (or
16of all Link Flows) being reset, then it shall send a ResetTxIndication message and enter the
17RLP Reset State.
15
Upon entering the RLP Reset state RLP transmitter shall:
18
19
20
21
22
Perform the RLP transmitter initialization procedure defined in 2.5.4.1.1.1.1 of [3] for the
Route being reset.
If a Nak message is received for the Route of the Link Flow being reset while in the RLP
Reset state, the message shall be ignored.
25
If the RLP transmitter that initiated the reset procedure is an access terminal, and if a
PhysicalLayer.ReverseTrafficPacketsMissed indication is received for the Route of the Link
Flow being reset while RLP is in the Reset state, then the indication shall be ignored.
26
The RLP transmitter should not transmit RLP packets while in the RLP Reset state.
23
24
27
28
29
30
31
32
33
If RLP receives a ResetTxIndicationAck message for the Route of the Link Flow being reset
while in the RLP Reset state, it shall send a ResetTxComplete message back and leave the
RLP Reset state.
If RLP receives a SignalingAdaptation.ConnectionOpened indication, if the Protocol Subtype
of the Signaling Adaptation Protocol is not equal to 0x0000, otherwise if RLP receives an
IdleState.ConnectionOpened indication while in the RLP Reset state, it shall leave the RLP
Reset state.
If a ResetTxIndicationAck message is received for a Route while that Route is not in the RLP
Reset state, the message shall be ignored.
34
35
3.3.5 Reset Procedure for Initiating Side when it is an RLP Receiver
36
37
3GPP2 C.P0087-0 v0.83
If the side initiating a reset procedure is an RLP receiver for the Route of the Link Flow being
2reset, then it shall send a ResetRxIndication message and enter the RLP Reset State. Upon
3entering the RLP Reset state, the RLP receiver shall:
1
4
5
6
7
8
9
10
11
12
13
Perform the RLP receiver initialization procedure defined in 2.5.4.1.1.1.2 of [3] for the Route
being reset.
Ignore all RLP data units received for the Route of the Link Flow being reset while in the
RLP Reset state.
When RLP receives a ResetRxComplete message for the Route of the Link Flow being reset,
it shall leave the RLP Reset state.
of the Signaling Adaptation Protocol is not equal to 0x0000, otherwise if the RLP receives
an IdleState.ConnectionOpened indication while in the RLP Reset state, it shall leave the
RLP Reset state.
If a ResetRxComplete is received for a Route while the Route is not in the RLP Reset state, the
15message shall be ignored.
14
3.3.6 Reset Procedure for the Responding Side when it is an RLP Receiver
16
17
If the side responding to a reset procedure is an RLP receiver for the Route of the Link Flow
19being reset, then it shall respond with a ResetTxIndicationAck message upon receiving a
20ResetTxIndication message. After sending the message it shall enter the RLP Reset state for the
21Route being reset, if it was not already in the RLP Reset state. Upon entering the RLP Reset
22state RLP shall:
18
23
24
25
26
27
28
29
30
31
32
Perform the RLP receiver initialization procedure defined in 2.5.4.1.1.1.2 of [3] for the Route
being reset.
Ignore all RLP data units received for the Route of the Link Flow being reset while in the
RLP Reset state.
When RLP receives a ResetTxComplete message for the Route of the Link Flow being reset,
it shall leave the RLP Reset state.
of the Signaling Adaptation Protocol is not equal to 0x0000, otherwise if RLP receives an
IdleState.ConnectionOpened indication while in the RLP Reset state, it shall leave the RLP
Reset state.
If a ResetTxComplete message is received for a Route while the Route is not in the RLP Reset
34state, the message shall be ignored.
33
3.3.7 Reservation State Maintenance for RLP Transmit Procedures
35
36
37
3GPP2 C.P0087-0 v0.83
The ReservationLabel parameter of the FlowNNReservationFwd or FlowNNReservationRev

2attribute indicates the higher layer flows associated with Link Flow NN. Each ReservationLabel
3shall be associated with no more than one forward Link Flow. Each ReservationLabel shall be
4associated with no more than one reverse Link Flow.
1
Each Reservation can be in one of the following two states:
Close State
Open State
The transmitter should transmit higher layer octets 4 or packets using the Link Flow associated
9with the higher layer flow if the associated Link Flow is activated and if the Reservation is in
10the Open state. The transmitter should transmit higher layer octets belonging to a higher layer
11flow that is not associated with any Link Flow using the Link Flow with ReservationLabel 0xff
12if the higher layer flow provides an octet stream with octet-based HDLC-like framing to the
13Enhanced Multi-flow Packet Application. The transmitter may transmit higher layer octets
14belonging to a higher layer flow identified by a Reservation that is in the Close state using the
15Link Flow with ReservationLabel 0xff if the higher layer flow provides an octet stream with
16octet-based HDLC-like framing to the Enhanced Multi-flow Packet Application. The transmitter
17may transmit higher layer octets belonging to a higher layer flow identified by a Reservation
18that is bound to a de-activated Link Flow using the Link Flow with ReservationLabel 0xff if the
19higher layer flow provides an octet stream with octet-based HDLC-like framing to the Enhanced
20Multi-flow Packet Application. The transmitter should transmit higher layer packets belonging
21to a higher layer flow that is not associated with any Link Flow using the Link Flow with
22ReservationLabel 0xfe if the higher layer flow provides an IP packet stream to the Enhanced
23Multi-flow Packet Application. The transmitter may transmit higher layer packets belonging to
24a higher layer flow identified by a Reservation that is in the Close state using the Link Flow
25with ReservationLabel 0xfe if the higher layer flow provides an IP packet stream to the
26Enhanced Multi-flow Packet Application. The transmitter may transmit higher layer packets
27belonging to a higher layer flow identified by a Reservation that is bound to a de-activated Link
28Flow using the Link Flow with ReservationLabel 0xfe if the higher layer flow provides an IP
29packet stream to the Enhanced Multi-flow Packet Application.
8
The access terminal and the access network shall not perform any actions that will result in
31the number of Reverse Link Reservations in the Open state to exceed the value specified by
32MaxNumOpenReservationsRev. The access terminal and the access network shall not perform
33any actions that will result in the number of Forward Link Reservations in the Open state to
34exceed the value specified by MaxNumOpenReservationsFwd.
30
Figure 3.3.7 -3 and Figure 3.3.7 -4 show the state transition diagram at the access terminal
36and
the
access
network.
State
transitions
that
may
be
caused
by
37ConnectedState.ConnectionClosed,
and
38RouteUpdate.ConnectionLost indications are not shown.
35
Higher
layer
is
represented
4FlowNNFlowProtocolParametersRev
by
ProtocolID
field
of
the
FlowNNFlowProtocolParametersFwd/
attribute of the respective link flow NN.
10
3GPP2 C.P0087-0 v0.83
Initial State
of Reservations other
than 0xff and 0xfe
Initial State
of Reservations 0xff
and 0xfe
Rx ReservationAccept for a ReservationOnRequest
or Rx RevReservationOn
Open State
Close State
Rx ReservationAccept for a ReservationOffRequest

or Rx RevReservationOff
Figure 3.3.7-3. Reverse Link Reservation State Diagram (Access Terminal)
Initial State
Initial State
of Reservations 0xff
of Reservations other
and 0xfe
than 0xff and 0xfe
Tx ReservationAccept for a ReservationOnRequest
or Tx an RLP packet for this Reservation
Or Tx FwdReservationOn
Open State
Close State
Tx ReservationAccept for a ReservationOffRequest
Figure 3.3.7-4. Forward Link Reservation State Diagram (Access Network)
3.3.8 Access Terminal Requirements for Close State
This section supersedes section 2.5.4.2.1.1.2.1 of [3].
The access terminal shall not transmit PDUs from higher layer flows belonging to this
10Reservation using any Link Flow other than the Link Flow associated with ReservationLabel
110xff if the higher layer flow provides an octet stream with octet-based HDLC-like framing to the
12Enhanced Multi-flow Packet Application. The access terminal shall not transmit PDUs from
13higher layer flows belonging to this Reservation using any Link Flow other than the Link Flow
14associated with ReservationLabel 0xfe if the higher layer flow provides an IP packet stream to
15the
Enhanced Multi-flow Packet Application. The access terminal may send a
9
11
3GPP2 C.P0087-0 v0.83
ReservationOnRequest message to request transition of the Reservation to the Open state 5. The
2access terminal may re-send a ReservationOnRequest message if it does not receive a
3corresponding ReservationAccept or ReservationReject message within
the time period
4specified
by TRLPResponse of sending the ReservationOnRequest message. If the
5ReservationOnRequest message contains a reverse Reservation, then the Reservation shall
6transition
to the Open state when the access terminal receives the corresponding
7ReservationAccept message.
1
Upon receiving a RevReservationOn message, the access terminal shall transition the
9Reservation to the Open state. Upon receiving a SignalingAdaptation.ConnectionOpened
11otherwise upon receiving an IdleState.ConnectionOpened indication, the access terminal shall
12transition the Reservations to the Open State whose corresponding ReservationKKIdleStateRev
13attribute is 0x02, where KK is the two-digit hexadecimal ReservationLabel in the range 0x00 to
140xff inclusive.
8
3.3.9 Access Network Requirements for Close State
15
This section supersedes section 2.5.4.2.1.1.2.2 of [3].
16
If the Reservation entered this state as a result of any condition other than the following
conditions, then the access network shall send a FwdReservationOff message upon entering
19this state:
17
18
20
21
22
23
24
the access network transmitted a ReservationAccept message in response to a

ReservationOffRequest message requesting to transition the Reservation to the Close state,
or
ReservationKKIdleStateFwd attribute of the Reservation is 0x01 or 0x02, and the
Reservation transitioned to the Close state because the Connection was closed or lost.
Upon sending a ReservationAccept message for a forward Reservation in response to a

26ReservationOnRequest message, the access network shall transition the Reservation to the
27Open state.
25
Upon sending a FwdReservationOn message, the access network shall transition the
29Reservation to the Open state. Upon receiving a SignalingAdaptation.ConnectionOpened
31otherwise upon receiving an IdleState.ConnectionOpened indication, the access network shall
32transition the Reservations to the Open state whose corresponding ReservationKKIdleStateFwd
33attribute is 0x02, where KK is the two-digit hexadecimal ReservationLabel in the range 0x00 to
340xff inclusive.
28
The access network may transmit SDUs from higher layer flows belonging to this Reservation
36using the Link Flow to which the Reservation is bound. Upon doing so, the access network
37shall transition the Reservation to the Open State.
35
5 Note that the ReservationOnRequest message supports requests for multiple Reservations on both the
3forward
and reverse links. This arrangement allows requests for groups of Reservations (e.g., for
4bidirectional
higher layer application flows) to be combined in the same ReservationOnRequest message.
12
3GPP2 C.P0087-0 v0.83
3.3.10 Access Terminal Requirements for Open State
This section supersedes 2.5.4.2.1.1.3.1 of [3].
The access terminal may transmit PDUs from higher layer flows belonging to this Reservation
using the Link Flow to which the Reservation is bound.
4
5
The access terminal may send a ReservationOffRequest message to request the transition of a
7Reservation to the Close state. The access terminal may re-send a ReservationOffRequest
8message if it does not receive a ReservationAccept or ReservationReject message within the
9time period specified by T RLPResponse of sending the ReservationOffRequest message. If the
10ReservationOffRequest message contains a reverse Reservation, then the access terminal shall
11transition
the Reservation to the Close state when the access terminal receives a
12ReservationAccept message.
6
Upon receiving a RevReservationOff message, the access terminal shall transition the
14Reservation to the Close state. Upon receiving a SignalingAdaptation.ConnectionClosed
16otherwise upon receiving a ConnectedState.ConnectionClosed indication, the access terminal
17shall
transition
to
the
Close
state
Reservations
whose
corresponding
18ReservationKKIdleStateRev attribute is 0x01 or 0x02 unless an access network initiated
6
19Connection is being opened at the same time , where KK is the two-digit hexadecimal
20ReservationLabel. Upon receiving a SignalingAdaptation.ConnectionFailed indication, if the
21Protocol Subtype of the Signaling Adaptation Protocol is not equal to 0x0000, otherwise upon
22receiving an IdleState.ConnectionFailed indication, the access terminal shall transition to the
23Close state Reservations whose corresponding ReservationKKIdleStateRev attribute is 0x01 or
240x02, where KK is the two-digit hexadecimal ReservationLabel.
13
3.3.11 Access Network Requirements for Open State
25
This section supersedes 2.5.4.2.1.1.3.2 of [3].
26
The access network may transmit PDUs from higher layer flows belonging to this Reservation
28using the Link Flow to which the Reservation is bound.
27
29
30
31
Upon sending a ReservationAccept message for a forward Reservation in response to a

ReservationOffRequest message, the access network shall transition the Reservation to the
Close state.
Upon receiving
32
35
a SignalingAdaptation.ConnectionClosed indication, if the Protocol Subtype of the Signaling

Adaptation Protocol is not equal to 0x0000, otherwise a ConnectedState.ConnectionClosed
or
36
a RouteUpdate.ConnectionLost indication,
33
34
An access
network
can
3TrafficChannelAssignment
send
ConnectionClose
message
of Connected
State Protocol and
message of Route Update Protocol in the same security layer packet.
13
3GPP2 C.P0087-0 v0.83
the access network shall transition to the Close state Reservations whose corresponding
2ReservationKKIdleStateFwd attribute is 0x01 or 0x02 unless an access network initiated
3Connection is being opened at the same timeError: Reference source not found, where KK is
4the two-digit hexadecimal ReservationLabel. Upon receiving
1
a RouteUpdate.ConnectionLost or
a SignalingAdaptation.ConnectionFailed indication, if the Protocol Subtype of the Signaling

Adaptation Protocol is not equal to 0x0000, otherwise a IdleState.ConnectionFailed
indication,
5
6
7
8
the access network shall transition to the Close state Reservations whose corresponding
ReservationKKIdleStateFwd attribute is 0x01 or 0x02, where KK is the two-digit hexadecimal
11ReservationLabel.
9
10
If, for any KK, all of the following conditions are true, the access network shall take action
within TTurnaround, where TTurnaround is equal to 2 seconds, such that at least one of the following
14conditions
would
no longer be true (e.g., by modifying
the value of
15ReservationKKQoSResponseFwd or by transitioning forward Reservation KK to the Close state):
12
13
16
ReservationKKQoSRequestFwd is set to a non-default value.
17
Forward Reservation KK is in the Open state.
18
19
20
21
ReservationKKQoSResponseFwd is set to the default value or the QoS_ATTRIBUTE_SET_ID

field in ReservationKKQoSResponseFwd is not equal to the value of any
QoS_ATTRIBUTE_SET_ID field in the corresponding ReservationKKQoSRequestFwd
attribute (see [3].)
If, for any KK, all of the following conditions are true, the access network shall take action
within TTurnaround, where TTurnaround is equal to 2 seconds, such that at least one of the following
24conditions
would
no longer be true (e.g., by modifying
the value of
25ReservationKKQoSResponseRev or by transitioning reverse Reservation KK to the Close state):
22
23
26
ReservationKKQoSRequestRev is set to a non-default value.
27
Reverse Reservation KK is in the Open state.
28
29
30
31
ReservationKKQoSResponseRev is set to the default value or the QoS_ATTRIBUTE_SET_ID

field in ReservationKKQoSResponseRev is not equal to the value of any
QoS_ATTRIBUTE_SET_ID field in the corresponding ReservationKKQoSRequestRev
attribute (see [3].)
3.3.12 Indications for Interface to Other Protocols with Radio Link Protocol
32
33
34
35
36
37
IdleState.ConnectionFailed
38
SignalingAdaptation.ConnectionFailed
14
3GPP2 C.P0087-0 v0.83
PhysicalLayer.ReverseTrafficPacketsMissed along with parameters indicating the Link Flow

number and missing data units.
15
3GPP2 C.P0087-0 v0.83
3.4 Additional Requirement to support eHRPD operation
This section describes additional requirements from [3] for the access terminal and the access
network supporting eHRPD operation.
3
4
The access terminal that supports eHRPD operation shall include indicate that ProtocolID
0x07 (see [4]) is supported in the ATSupportedFlowProtocolParametersPP attribute.
5
6
If the ATSupportedFlowProtocolParametersPP attribute includes indicates ProtocolID 0x07 is

8supported and the access network selects eHRPD operation, the access network shall negotiate
9the
ProtocolID
field
of
the
FlowNNFlowProtocolParametersFwd
and
10FlowNNFlowProtocolParametersRev
attributes to 0x07 for the Link Flow bound to
11ReservationLabel 0xFF.
7
When
If
the
ProtocolID
field
of
the
FlowNNFlowProtocolParametersFwd
and
13FlowNNFlowProtocolParametersRev attributes is are set to 0x07 for the Link Flow bound to
14ReservationLabel 0xFF, the following requirements shall apply to both the access terminal and
15the access network:
12
17
the ReservationLabel of each Reservations except ReservationLabel 0xFF and 0xFE shall be
set as follows (see [5] ):
18
The upper four bits of the ReservationLabel shall be set to the PDN-ID that the
Reservation is associated with. The PDN-ID shall be in the range 0000 to 1110If the
Reservation is associated with the default PDN, the upper four bits shall be set to
1111.
The lower four bits shall be set to identify the Reservation for the PDN identified by the
upper four bits. Figure 3.1-1 shows the ReservationLabel format.
16
19
20
21
22
23
24
Figure 3.1-1. ReservationLabel format
25
26
27
28
29
If ReservationLabel 0xFE is bound to an active Link Flow, then the ProtocolID field of the
FlowNNFlowProtocolParametersFwd and FlowNNFlowProtocolParametersRev attributes
shall be set to 0x08 (see [4]) for that Link Flow. The ProtocolID field shall not be set to 0x08
for other Link Flow.
31
If the ProtocolID field of the FlowNNFlowProtocolParametersFwd attribute is not set to 0x07

or 0x08 for a Link Flow NN:
32
30
33
34
35
The upper four bits of each ReservationLabel field bound to the Link Flow in the
FlowNNReservationFwd attribute shall be the same value.
If the ProtocolID field of the FlowNNFlowProtocolParametersRev attribute is not set to 0x07

or 0x08 for a Link Flow NN:
16
3GPP2 C.P0087-0 v0.83
1
2
The upper four bits of each ReservationLabel field bound to the Link Flow in the
FlowNNReservationRev attribute shall be the same value.
17
3GPP2 C.P0087-0 v0.83
4 SESSION LAYER
(Editor note (open issue): When the access terminal boots up in E-UTRAN and has a prior
4session or when performs an idle handoff from HRPD to EUTRAN and has a session, is TBD
5how the access terminal will handle the session)
3
4.1 Default Session Management Protocol
4.1.1 Deactivate for the InUse Instance of the Protocol
This section supersedes 7.2.6.1.1.2 of [1].
If the access terminal receives a Deactivate command in the Inactive State, the command shall
10be ignored.
9
If the access terminal receives a Deactivate command in any state other than the Inactive
State, the access terminal shall perform the following:
11
12
13
Send a SessionClose message to the access network.
16
Issue a SignalingAdaptation.CloseConnection command, if the Protocol Subtype of the

Signaling Adaptation Protocol is not equal to 0x0000, otherwise the protocol shall issue an
AirLinkManagement.CloseConnection command.
17
Issue an AddressManagement.Deactivate command.
18
Issue a SessionConfiguration.Deactivate command.
19
Return a SessionClosed indication.
20
Transition to the Inactive State.
14
15
If the access network receives a Deactivate command in the Close State, the command shall be
22ignored.
21
If the access network receives a Deactivate command in any state other than the Close State,
the access network shall send a SessionClose message and transition to the Close State.
23
24
4.1.2 Processing the SessionClose Message
25
26
If the access terminal receives a SessionClose message in the Inactive State, the message shall
be ignored.
27
28
If the access terminal receives a SessionClose message in any state other than the Inactive
30State, the access terminal shall perform the following:
29
31
32
33
34

1
3GPP2 C.P0087-0 v0.83
If the access network receives a SessionClose message in the Close State, the access network
6shall process it as specified in 4.1.5.
5
If the access network receives a SessionClose message in any state other than the Close State,
the access network shall:
7
8
11

12
13
14
15
Transition to the AMP Setup State.
9
10
4.1.3 Processing Failed Indications
16
17
The
access
terminal
shall
ignore
an
AddressManagement.Failed,
or
a
SessionConfiguration.Failed indication, if the access terminal receives the indication in the
20Inactive State.
18
19
If the access terminal receives a SessionConfiguration.Failed indication while in any state other
than the Inactive State, then the access terminal shall perform the following:
21
22
23
26

27
28
29
30
The access terminal shall transition to the Inactive State.
24
25
If the access terminal receives an AddressManagement.Failed indication while in any state

32other than the Inactive State, then the access terminal shall perform the following:
31
35

36
33
34
3GPP2 C.P0087-0 v0.83
If the access network receives an AddressManagement.Failed, or a SessionConfiguration.Failed

5indication, the access network shall perform the following:
4
Send a SessionClose message to the access terminal.
Transition to the Close State.
4.1.4 Keep Alive Functions
The access terminal and the access network shall monitor the traffic flowing on the Forward
11Channel and Reverse Channel, respectively, directed to or from the access terminal. If either
12the access terminal or the access network detects a period of inactivity of at least
13TSMPClose/NSMPKeepAlive minutes,
10
16
If the Protocol Subtypeprotocol subtype of the Signaling Adaptation Protocol is not equal to
0x0000 and TunnelModeEnabled, provided as public data of the Signaling Adaptation
Protocol, is not equal to 0,
17
14
15
The access network should not issue send a KeepAliveRequest message.
21
Protocol, is not equal to 0 and HRPDPreRegistrationAllowed, provided as public data of the
Address ManagementOverhead Messages Protocol, is set to 1,
22
18
19
20
The access terminal should issue send a KeepAliveRequest message.
26
Protocol, is not equal to 0 and HRPDPreRegistrationAllowed, provided as public data of the
Address ManagementOverhead Messages Protocol, is set to 0,
27
23
24
25
28
29
The access terminal shall not issue send a KeepAliveRequest message.
Otherwise the access terminal or the access network may send a KeepAliveRequest
message.
The recipient of the message shall respond by sending the KeepAliveResponse message. When
31a KeepAliveResponse message is received, the access terminal shall not send another
32KeepAliveRequest message for at least TSMPClose/NSMPKeepAlive minutes.
30
If the access terminal does not detect any traffic from the access network directed to it for a
34period of at least TSMPClose minutes, it shall perform the following:
33
35
36
37

3GPP2 C.P0087-0 v0.83
If the access network does not detect any traffic from the access terminal directed to it for a
6period of at least TSMPClose minutes, it should perform the following:
5
7
8
9

10
11
12
13
If the value of T SMPClose is set to zero, the access terminal and the access network shall not send
or expect keep-alive messages, and shall disable the transitions occurring as a consequence of
16not receiving these messages.
14
15
4.1.5 Close State
17
18
The Close State is associated only with the protocol in the access network. In this state the
20protocol in the access network waits for a SessionClose message from the access terminal or
21an expiration of a timer.
19
The access network shall set the Close State timer upon entering this state. The value of this
23timer shall be set to TSMPClose or TSMPMinClose, whichever is larger.
22
When the access network receives a SessionClose message or when the Close State timer
expires the protocol shall:
24
25
28

29
30
31
32
26
27
While in this state, if the access network receives any packet from the access terminal which is
34addressed by the UATI assigned during this session and contains anything but a SessionClose
35message, it shall stay in the Close State and perform the following:
33
36
Discard the packet.

4
3GPP2 C.P0087-0 v0.83
Respond with a SessionClose message.
4.1.6 Commands Sent
AddressManagement.Activate
SessionConfiguration.Activate
AddressManagement.Deactivate
SessionConfiguration.Deactivate
AirLinkManagement.CloseConnection
SignalingAdaptation.CloseConnection
10
4.1.7 HRPD to E-UTRAN Idle Handoff Procedure and HRPD Prior Session Handling
11
This is a new section under 7.2 of [1].
12
If the access terminal has a HRPD session and the primary radio-access-technology is E14UTRAN, the access terminal shall:
13
15
16
17
If the HRPD session has at least one personality with the Signaling Adaptation Protocol
subtype not equal to 0x0000 which can be used for E-UTRAN interworking, the access
terminal may try to restore the HRPD session over the tunnel.
20
Otherwise, if the Address Management Protocol in the access terminal is in the Open State
and HRPDPreregistrationAllowed public data of the Overhead Messages Protocolis is set to
1, the access terminal shall:
21
Purge the HRPD session.
22
Follow the Access Terminal Bootup Procedures from 2.1.
18
19
3GPP2 C.P0087-0 v0.83
4.2 Default Session Configuration Protocol
4.2.1 Maintaining the ConnectionState Parameter
Upon receiving a SignalingAdaptation.ConnectionOpened indication, if the Protocol Subtype of

6the Signaling Adaptation Protocol is not equal to 0x0000, otherwise upon receiving an
7IdleState.ConnectionOpened indication, the access terminal and the access network shall set
8ConnectionState to Connected.
5
Upon receiving a SignalingAdaptation.ConnectionClosed indication, if the Protocol Subtype of

10the Signaling Adaptation Protocol is not equal to 0x0000, otherwise upon receiving a
11ConnectedState.ConnectionClosed or upon receiving a RouteUpdate.ConnectionLost indication,
12the access network shall set ConnectionState to Closed.
9

the Signaling Adaptation Protocol is not equal to 0x0000, otherwise upon receiving a
15ConnectedState.ConnectionClosed indication, the access terminal shall set ConnectionState to
16Closed.
13
14
4.2.2 Maintaining the ConfigurationLock Parameter
17
18
The access terminal and the access network shall maintain a parameter called
20ConfigurationLock. If the value of the SupportConfigurationLock attribute is 0x0001, then the
21access terminal and the access network shall support the processing of the LockConfiguration,
22LockConfigurationAck, UnLockConfiguration, and UnLockConfigurationAck messages. If the
23value of the SupportConfigurationLock attribute is not 0x0001, then the access network shall
24not transmit a LockConfiguration or UnLockConfiguration message. If the access network
25sends a LockConfiguration message, it shall set ConfigurationLock to Locked. If the access
26network sends an UnLockConfiguration message, it shall set ConfigurationLock to UnLocked.
19
If the access terminal receives a LockConfiguration message, then the access terminal shall
respond with a LockConfigurationAck message and shall set ConfigurationLock to Locked.
27
28
If the access network does not receive a LockConfigurationAck message within an

30implementation specific time interval in response to a LockConfiguration message, then the
31access network may retransmit the LockConfiguration message an implementation specific
32number of times.
29
If the access network does not receive an UnLockConfigurationAck message within an

implementation specific time interval in response to an UnLockConfiguration message, then
35the access network may retransmit the UnLockConfiguration message an implementation
36specific number of times.
33
34
3GPP2 C.P0087-0 v0.83
If the access terminal receives an UnLockConfiguration message, then the access terminal
2shall respond with an UnLockConfigurationAck message and shall set ConfigurationLock to
3UnLocked.
1
Upon receiving a
SignalingAdaptation.ConnectionClosed indication, if the Protocol Subtype of the Signaling

Adaptation Protocol is not equal to 0x0000, otherwise upon receiving a
ConnectedState.ConnectionClosed or
RouteUpdate.ConnectionLost indication,
5
6
the access network shall set ConfigurationLock to UnLocked.

11the Signaling Adaptation Protocol is not equal to 0x0000, otherwise upon receiving a
12ConnectedState.ConnectionClosed indication, the access terminal shall set ConfigurationLock
13to UnLocked.
10
4.2.3 Access Terminal Requirements of AN Initiated State
14
15
In this protocol state the access terminal shall be ready to execute the access network-initiated
17configuration procedures particular to each protocol used during the session.
16
If the access terminal receives a ConfigurationRequest message from the access network, it
shall process it and shall respond with a ConfigurationResponse message according to the
20Generic Configuration Protocol.
18
19
Once the access terminal and the access network agree upon a new protocol subtype for a
protocol Type (per the Generic Configuration Protocol), the access terminal shall purge the
23existing InConfiguration protocol instance corresponding to the protocol type and subtype and
24create an InConfiguration protocol instance corresponding to the agreed upon protocol
25subtype.
21
22
If the access terminal receives an AttributeUpdateRequest message requesting to update the

value of the Session Configuration Token in this state, then the access terminal shall ignore
28the message.
26
27
If the access terminal receives a SoftConfigurationComplete message, it shall perform the

following:
29
30
31
32
33
The Session Configuration Protocol shall store the InConfiguration protocol and application
instances as a personality that is identified by the PersonalityIndexStore field of the
SoftConfigurationComplete message.
35
If the Continue field of the SoftConfigurationComplete message is set to 1, then the access
terminal shall transition to the AT Initiated State.
36
Otherwise, the access terminal shall perform the following:
34
37
3GPP2 C.P0087-0 v0.83
If the Commit field of the SoftConfigurationComplete message is set to 1, then the access
2terminal shall perform the following:
1
3
4
5
6
{
Return a Reconfigured indication.
When ConnectionState is Closed:
{
If as a result of ConfigurationRequest/ConfigurationResponse exchange a
PriorSession attribute with a non-zero Restore field is agreed upon, then all the session
state information (except the SessionConfigurationToken which is set to the value
specified in the SoftConfigurationComplete message) corresponding to the session
specified by the PriorSession attribute shall take effect.
10
11
12
13
14
15
Otherwise,
16
{
The Session Configuration Protocol shall set the protocols and attributes of the
InConfiguration protocol instances to the corresponding protocols and attribute
values of the stored personality with index equal to the value of the four most
significant bits of the SessionConfigurationToken.
17
18
19
20
22
The Session Configuration Protocol shall direct all the InConfiguration protocol
instances to execute their Commit procedures.
23
21
24
25
The protocol shall set the SessionConfigurationToken public data to the value specified in
the SoftConfigurationComplete message.
26
27
28
Transition to the Open State.
29
If the access terminal receives a ConfigurationComplete message it shall perform the following:
30
33

34
35
36
31
32
3GPP2 C.P0087-0 v0.83
The protocol shall set the SessionConfigurationToken public data to the value specified
in the ConfigurationComplete message,
If as a result of ConfigurationRequest/ConfigurationResponse exchange a PriorSession

attribute with a non-zero Restore field is agreed upon, then
2
3
4
5
6
7
8
9
10
all the session state information (except the SessionConfigurationToken which is set
to the value specified in the ConfigurationComplete message) corresponding to the
session specified by the PriorSession attribute shall take effect.
Otherwise,
4.2.4 Access Network Requirements of AN Initiated State
11
12
In this protocol state, the access network may execute the access network-initiated
14configuration procedures that are particular to each protocol used during the session.
13
The access network shall not send an AttributeUpdateRequest message requesting to update
the value of the Session Configuration Token in this state 7. The access network shall not send
17the ATSupportedApplicationSubtypes attribute in the ConfigurationRequest message.
15
16
If the access network chooses to negotiate a different Session Configuration Protocol, it shall
initiate the Session Configuration Protocol selection (i.e., sending a ConfigurationRequest
20message specifying protocol Type of NSCPType) prior to selection of any other protocol.
18
19
The access network may set the SessionConfigurationToken field of the ConfigurationComplete
or SoftConfigurationComplete message to reflect the selected protocols and the negotiation
23parameters associated with the negotiated protocols. If PersonalityCount is greater than one,
24then the four most significant bits of the SessionConfigurationToken field shall be set to the
25index of the personality that is to take effect when the protocol transitions to the Open State. If
26PersonalityCount is greater than one, and if a PriorSession attribute with Restore field set to 1
27is negotiated, then the access network shall set the four most significant bits of the Session
28Configuration Token to the corresponding bits of the Session Configuration Token associated
29with the prior session. The rules for setting the twelve least significant bits of the Session
30Configuration Token are outside the scope of this specification.
21
22
Once the access terminal and the access network agree upon a new protocol subtype for a
32protocol Type (per the Generic Configuration Protocol), the access network shall purge the
33existing InConfiguration protocol instance corresponding to the protocol type and subtype and
34create an InConfiguration protocol instance corresponding to the agreed upon protocol.
31
7 If the access network wants to switch personalities, the access network can close the connection and
3then
send
an
AttributeUpdateRequest
message
4SessionConfigurationToken.
requesting
to
update
the
value
of
the
3GPP2 C.P0087-0 v0.83
The access network shall not send a SoftConfigurationComplete message if PersonalityCount is

2one. The access network shall not send a ConfigurationComplete message if PersonalityCount
3is greater than one.
1
The access network shall send a SoftConfigurationComplete message with Continue field set to
51 if all of the following conditions are satisfied:
4
PersonalityCount is greater than one.
The protocol in the access network requires no further negotiation of protocols or

configuration of negotiated protocols for this personality.
The access network wants to create and store more personalities.
The access network shall send a SoftConfigurationComplete message with Continue field set to
110 if all of the following conditions are satisfied:
10
12
PersonalityCount is greater than one.
14
The protocol in the access network requires no further negotiation of protocols or

configuration of negotiated protocols for this personality.
15
The protocol in the access network requires no further creation and storing of personalities.
13
The
access
network
shall
not
set
the
PersonalityIndexStore
field
of
the
17SoftConfigurationComplete message to zero if HardLink protocol subtype has been negotiated
18for one or more of the InConfiguration protocol instances. The access network shall set the
19PersonalityIndexStore field of the SoftConfigurationComplete message to zero if a Personality
20with index zero is not already stored.
16
The access network shall set Commit field of the SoftConfigurationComplete message to 1 if
22any of the following conditions is true:
21
23
24
25
26
27
28
29
The session configuration has resulted in any change to the personality that is currently in
use.
The four most significant bits of the SessionConfigurationToken field of the
SoftConfigurationComplete message are different from those of the previous Session
Configuration Token.
A PriorSession attribute with a non-zero Restore field is agreed upon during the session
configuration.
Upon sending a SoftConfigurationComplete message, the access network shall perform the
following:
30
31
32
33
34
The Session Configuration Protocol shall store the InConfiguration protocol and application
instances as a personality that is identified by the PersonalityIndexStore field of the
SoftConfigurationComplete message.
36
If the Continue field of the SoftConfigurationComplete message is set to 1, then the access
network shall transition to the AT Initiated State.
37
Otherwise, the access network shall perform the following:
35
38
10
3GPP2 C.P0087-0 v0.83
If the Commit field of the SoftConfigurationComplete message is set to 1, then the access
2network shall perform the following:
1
3
4
5
6
{
{
If as a result of ConfigurationRequest/ConfigurationResponse exchange a
PriorSession attribute with a non-zero Restore field is agreed upon, then all the session
state information (except the SessionConfigurationToken which is set to the value
specified in the SoftConfigurationComplete message) corresponding to the session
specified by the PriorSession attribute shall take effect.
10
11
12
13
14
15
Otherwise,
16
{
The Session Configuration Protocol shall set the protocols and attributes of the
InConfiguration protocol instances to the corresponding protocols and attribute
values of the stored personality with index equal to the value of the four most
significant bits of the SessionConfigurationToken.
17
18
19
20
22
23
21
24
25
The protocol shall set the SessionConfigurationToken public data to the value specified in
the SoftConfigurationComplete message.
26
27
28
29
If the protocol in the access network requires no further negotiation of protocols or

31configuration of negotiated protocols and if PersonalityCount is one, then the access network
30
33
Send a ConfigurationComplete message to the access terminal.
36

37
34
35
11
3GPP2 C.P0087-0 v0.83
The protocol shall set the SessionConfigurationToken public data to the value specified
in the ConfigurationComplete message, and
If as a result of ConfigurationRequest/ConfigurationResponse exchange a PriorSession

attribute with a non-zero Restore field is agreed upon, then all the session state
information (except the SessionConfigurationToken which is set to the value specified in
the ConfigurationComplete message) corresponding to the session specified by the
PriorSession attribute shall take effect.
Otherwise,
4
5
6
7
8
9
10
11
The protocol shall set the SessionConfigurationToken public data to the value
specified in the ConfigurationComplete message, and
12
13
14
4.2.5 Access Terminal Requirements of Open State
15
16
While in this state, the access terminal may send a ConfigurationRequest message to start the
18negotiation process (e.g., the access terminal may send this message to negotiate a new
19stream) if the value of the ConfigurationLock parameter is UnLocked. The access terminal shall
20not start a negotiation process if the value of the ConfigurationLock parameter is Locked.
21Starting the configuration process is defined as sending a ConfigurationRequest message, or
22AttributeUpdateRequest message defined by any protocol, or sending any other message that
23will initiate a process to change attribute values.
17
The access terminal shall ignore a ConfigurationComplete or SoftConfigurationComplete

25message received in this state.
24
The protocol in the access terminal shall transition to the AT Initiated State when any of the
following occurs:
26
27
28
The protocol in the access terminal receives a ConfigurationStart message,
29
The protocol in the access terminal sends a ConfigurationRequest message, or
30
31
The access terminal sends a message associated with the InConfiguration instance of any
other protocol.
If PersonalityCount is greater than one, and if the four most significant bits of this Session
Configuration Token are different from the index of the current Personality, and if
34ConnectionState is Closed, then the access terminal shall perform the following:
32
33
35
12
3GPP2 C.P0087-0 v0.83
1
2
3
4
5
6
7
8
9
10
11
The Session Configuration Protocol shall set the protocol subtypes, application subtypes,
and attributes of the stored copy of the personality that is currently in use to the
corresponding protocol subtypes, application subtypes, and attribute values of the InUse
instances of all protocols and applications.
and attributes of the InConfiguration instances of all protocols and applications to the
corresponding protocol subtypes, application subtypes, and attribute values of the stored
personality with index equal to the four most significant bits of the
SessionConfigurationToken.
The Session Configuration Protocol shall direct all the InConfiguration protocol instances
to execute their Commit procedures.
If the access terminal receives an AttributeUpdateAccept message in response to an

13AttributeUpdateRequest message proposing a value of the PriorSession attribute with non-zero
14Restore field, then the access terminal shall perform the following:
12
17
If ConnectionState is Opened, then issue a SignalingAdaptation.CloseConnection command,

if the Protocol Subtype of the Signaling Adaptation Protocol is not equal to 0x0000,
otherwise the protocol shall issue an AirLinkManagement.CloseConnection command.
18
15
16
19
20
21
When ConnectionState is Closed, all the Session State Information corresponding to the
session specified by the PriorSession attribute proposed in the AttributeUpdateRequest
message shall take effect.
If the access terminal receives a DeletePersonality message, then the access terminal shall
23perform the following:
22
25
Delete stored personalities

DeletePersonality message.
26
Send a DeletePersonalityAck message.
24
corresponding
to
the
PersonalityIndex
fields
of
the
4.2.6 Access Network Requirements of Open State
27
28
While in this state, the access network may send a ConfigurationStart message to start the
negotiation process (e.g., the access network may send this message to negotiate a new stream)
31if the value of the ConfigurationLock parameter is UnLocked. The access network shall not
32start a negotiation process if the value of the ConfigurationLock parameter is Locked. Starting
33the configuration process is defined as sending a ConfigurationRequest message, or
34AttributeUpdateRequest message defined by any protocol, or sending any other message that
35will initiate a process to change attribute values.
29
30
The protocol in the access network shall transition to the AT Initiated State when any of the
following occurs:
36
37
38
The protocol in the access network sends a ConfigurationStart message,
39
The protocol in the access network receives a ConfigurationRequest message, or
13
3GPP2 C.P0087-0 v0.83
1
2
The access network receives a message associated with the InConfiguration instance of any
other protocol.
If PersonalityCount is greater than one and if the four most significant bits of this Session
Configuration Token are different from the index of the current Personality, and if
5ConnectionState is Closed, then the access network shall perform the following:
3
4
6
7
8
9
10
11
12
13
14
15
16
17

and attributes of the stored copy of the personality that is currently in use to the
corresponding protocol subtypes, application subtypes, and attribute values of the InUse
instances of all protocols and applications.
and attributes of the InConfiguration instances of all protocols and applications to the
corresponding protocol subtypes, application subtypes, and attribute values of the stored
personality with index equal to the four most significant bits of the Session Configuration
Token.
The Session Configuration Protocol shall direct all the InConfiguration protocol instances
to execute their Commit procedures.
If the access network sends an AttributeUpdateAccept message in response to an

AttributeUpdateRequest message proposing a value of the PriorSession attribute with non-zero
20Restore field, then the access network shall perform the following:
18
19
23
If ConnectionState is Opened, then issue a SignalingAdaptation.CloseConnection command,

if the Protocol Subtype of the Signaling Adaptation Protocol is not equal to 0x0000,
otherwise the protocol shall issue an AirLinkManagement.CloseConnection command.
24
21
22
25
26
27
When ConnectionState is Closed, all the Session State Information corresponding to the
session specified by the PriorSession attribute proposed in the AttributeUpdateRequest
message shall take effect.
While in this state, the access network may send a DeletePersonality message instructing the
access terminal to delete stored personalities. Upon receiving a DeletePersonalityAck message
30in response to the DeletePersonality message, the access network shall delete stored
31personalities corresponding to the PersonalityIndex fields of the DeletePersonality message.
28
29
The access network shall not send the DeletePersonality message if PersonalityCount is equal
33to 0x0001. The PersonalityIndex field of the DeletePersonality message shall not be set to the
34index of the personality that is currently in use. The PersonalityIndex field of the
35DeletePersonality message shall not be set to the zero.
32
4.2.7 Commands
36
37
This protocol issues the following command:
38
39
14
3GPP2 C.P0087-0 v0.83
4.2.8 Indications
This protocol registers to receive the following indication:
10
15
3GPP2 C.P0087-0 v0.83
4.3 Inter-RATDefault Address Management Protocol
4.3.1 Overview
This section supersedes section 7.3.1 of [1].
The Inter-RATDefault Address Management Protocol provides the following functions:
Initial UATI assignment
Maintaining the access terminal unicast address as the access terminal moves between
HRPD subnets when the access terminal is receiving service inprimary radio access
technology is HRPD air interface or some other radio access technologies that support preregistration.
7
8
9
10
11
12
Maintaining the access terminal unicast address as the access terminal moves between
HRPD PreRegistrationZones when the access terminal is receiving service in E-UTRAN.
13
This protocol operates in one of three states:
14
15
16
17
18
19
20
21
22
23
Inactive State: In this state there are no communications between the access terminal and
the access network.
Setup State: In this state the access terminal and the access network perform a
UATIRequest/UATIAssignment/UATIComplete exchange to assign the access terminal a
UATI.
Open State: In this state the access terminal has been assigned a UATI. The access
terminal and access network may also perform a UATIRequest/UATIAssignment
/UATIComplete or a UATIAssignment/UATIComplete exchange so that the access terminal
obtains a new UATI.
The protocol states and the messages and events causing the transition between the states are
shown in Figure 4.2.1 -5 and Figure 4.2.1 -6.
24
25
16
3GPP2 C.P0087-0 v0.83
Failure transitions are not shown
Initial State
Tx UATIComplete
Rx Activate
Inactive
State
Setup
State
Open
State
Rx Deactivate
Rx Deactivate
1
2
3
Figure 4.2.1-5. Inter-RATDefault Address Management Protocol State Diagram (Access

Terminal)
Failure transitions are not shown
Initial State
Rx UATIComplete
Rx UATIRequest
Inactive
State
Setup
State
Open
State
Rx Deactivate
Rx Deactivate
4
5
6
Figure 4.2.1-6. Inter-RATDefault Address Management Protocol State Diagram (Access

Network)
4.3.2 Primitives and Public Data
4.3.2.1 Commands
This protocol defines the following command:
10
11
12
13
Activate
Deactivate
UpdateUATI
17
3GPP2 C.P0087-0 v0.83
4.3.2.2 Return Indications
This protocol returns the following indications:
Opened
UATIReleased
UATIAssigned
Failed
3
4
5
6
SubnetChanged
PreRegistrationZoneChanged
7
8
4.3.2.3 Public Data
Subtype for this protocol
ReceiveATIList
TransmitATI
SessionSeed
HRPDPreRegistrationAllowed
10
11
12
13
14
4.3.3 Connection Endpoints
15
The following Connection Endpoints are defined (to be used by the SLP):
16
17
18
19
20
The addresses specified by entries in the ReceiveATIList list whose ATIType is equal to 11
(i.e., RATI) or 10 (i.e., UATI) all define the same connection endpoint.
Each unique <ATI, Physical Layer Channel> where ATI is an entry in the ReceiveATIList
with ATIType equal to 00 (i.e., BATI), defines a separate Connection Endpoint.
4.3.4 Protocol Data Unit
21
The transmission unit of this protocol is a message. This is a control protocol and, therefore, it
does not carry payload on behalf of other layers or protocols.
22
23
This protocol uses the Signaling Application to transmit and receive messages.
24
4.3.5 Protocol Initialization
25
4.3.5.1 Protocol Initialization for the InConfiguration Protocol Instance
26
Upon creation, the InConfiguration instance of this protocol in the access terminal and the
28access network shall perform the following in the order specified:
27
29
30
The fall-back values of the attributes for this protocol instance shall be set to the default
values specified for each attribute.
18
3GPP2 C.P0087-0 v0.83
1
2
3
4
5
6
If the InUse instance of this protocol has the same protocol subtype as this InConfiguration
protocol instance, then the fall-back values of the attributes defined by the InConfiguration
protocol instance shall be set to the values of the corresponding attributes associated with
the InUse protocol instance.
The value for each attribute for this protocol instance shall be set to the fall-back value for
that attribute.
4.3.5.2 Protocol Initialization for the InUse Protocol Instance
Upon creation, the InUse instance of this protocol in the access terminal and access network
shall perform the following:
8
9
10
11
12
The value of the attributes for this protocol instance shall be set to the default values
specified for each attribute.
The protocol at the access terminal and the access network shall enter the Inactive State.
The protocol shall initialize the HRPDPreRegistrationAllowed field of the HRPDPreRegistration

record to 0.
13
14
4.3.6 Procedures and Messages for the InConfiguration Instance of the Protocol
15
4.3.6.1 Procedures
16
This protocol uses the Generic Configuration Protocol (see section 14.7 of [1]) to define the
18processing of the configuration messages.
17
4.3.6.2 Commit Procedures
19
The access terminal and the access network shall perform the procedures specified in this
21section, in the order specified, when directed by the InUse instance of the Session
22Configuration Protocol to execute the Commit procedures:
20
23
24
All the public data that are defined by this protocol, but are not defined by the InUse
protocol instance shall be added to the public data of the InUse protocol.
25
If the InUse instance of this protocol has the same subtype as this protocol instance, then
26
The access terminal and the access network shall set the attribute values associated
with the InUse instance of this protocol to the attribute values associated with the
InConfiguration instance of this protocol, and
The access terminal and the access network shall purge the InConfiguration instance of
the protocol.
27
28
29
30
33
If the InUse instance of this protocol does not have the same subtype as this protocol
instance, then the access terminal and the access network shall perform the following in
the order specified:
34
Set the initial state of the InConfiguration protocol instance to the Open State.
35
Set the receive pointer for UATIAssignment message validation, V(R), to 255.
31
32
19
3GPP2 C.P0087-0 v0.83
Set the UATI, UATIColorCode, and UATISubnetMask values associated with the InUse
instance of this protocol to the respective values associated with the InConfiguration
instance of this protocol.
The InConfiguration protocol instance shall become the InUse protocol instance for the
Address Management Protocol.
2
3
4
5
6
7
All the public data not defined by this protocol shall be removed from the public data of the
InUse protocol.
4.3.6.3 Message Formats
4.3.6.3.1 ConfigurationRequest
The ConfigurationRequest message format is as follows:
10
11
Field
Length (bits)
MessageID
TransactionID
Zero or more instances of the following record

AttributeRecord
Attribute dependent
MessageID
The sender shall set this field to 0x50.
TransactionID
The
sender
shall
increment
ConfigurationRequest message sent.
12
13
14
AttributeRecord
15
this
value
for
The format of this record is specified in section 14.3 of [1].
16
Channels
FTC
Addressing
SLP
RTC
Reliable
Priority
unicast
4.3.6.3.2 ConfigurationResponse
17
The ConfigurationResponse message format is as follows:
18
19
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
20
40
each
new
3GPP2 C.P0087-0 v0.83
MessageID
TransactionID
2
3
AttributeRecord
4
5
6
7
8
The sender shall set this value to the TransactionID field of the
corresponding ConfigurationRequest message.
An attribute record containing a single attribute value. If this message
selects a complex attribute, only the ValueID field of the complex
attribute shall be included in the message. The format of the
AttributeRecord is given in section 14.3 of [1]. The sender shall not
include more than one attribute record with the same attribute identifier.
Channels
Addressing
FTC
SLP
RTC
unicast
Reliable
Priority
40
4.3.7 Procedures and Messages for the InUse Instance of the Protocol
10
4.3.7.1 Procedures
11
4.3.7.1.1 Command Processing
12
4.3.7.1.1.1 Activate
13
If the protocol receives the Activate command in the Inactive State:
14
The access terminal shall transition to the Setup State.
The access network shall ignore the command.
15
16
If the protocol receives the Activate command in any state other than the Inactive State, the
18command shall be ignored.
17
4.3.7.1.1.2 Deactivate
19
If the protocol receives the Deactivate command in the Inactive State, the command shall be
21ignored.
20
If the protocol receives the Deactivate command in any state other than the Inactive State, the
protocol shall transition to the Inactive State and return a UATIReleased indication.
22
23
4.3.8 UpdateUATI
24
25
The access network and the access terminal shall ignore the UpdateUATI command when it is
received in any state other than the Open State.
26
27
If the access terminal receives an UpdateUATI command in the Open State, it shall set OldUATI
29to UATI and shall send a UATIRequest message except: when the protocol subtype of the
30Signaling Adaptation Protocol is equal to 0x0001 and TunnelModeEnabled public data of the
31Signaling Adaptation Protocol is set to 1 and HRPDPreRegistrationAllowed public data of the
28
21
3GPP2 C.P0087-0 v0.83
OverHead Management Protocol is set to 0, the access terminal shall not set OldUATI to UATI
2and shall not send a UATIRequest message.
1
If the access network receives an UpdateUATI command in the Open State, it may send a
UATIAssignment message.
3
4
A comprehensive list of events causing the UpdateUATI command is beyond the scope of this
6specification.
5
4.3.8.1.1 UATIAssignment Message Validation
Each time that the access network sends a new UATIAssignment message, it shall increment
9the value of the MessageSequence field.
8
The access terminal shall initialize a receive pointer for the UATIAssignment message
validation, V(R), to 255 when it sends a UATIRequest message and there exist an entry in the
12ReceiveATIList list whose ATIType field is equal to 11 (i.e., RATI).
10
11
When the access terminal receives a UATIAssignment message, it shall validate the message,
using the procedure defined in section 14.6 of [1] (S is equal to 8). The access terminal shall
15discard the message if it is invalid.
13
14
4.3.8.1.2 Processing HardwareIDRequest message
16
Upon reception of a HardwareIDRequest message, the access terminal shall respond with a
18HardwareIDResponse message. The access terminal shall set the HardwareID record of the
19HardwareIDResponse message to the unique ID that has been assigned to the terminal by the
20manufacturer.
17
4.3.9 Inactive State
21
22
In this state, there are no communications between the access terminal and the access
24network. The access terminal does not have an assigned UATI, the access network does not
25maintain a UATI for the access terminal, and may be unaware of the access terminals
26existence within its coverage area.
23
4.3.9.1 Access Terminal Requirements
27
Upon entering the Inactive State, the access terminal shall perform the following:
28
Set OldUATI to NULL.
Clear the ReceiveATIList
Add the following entry to the ReceiveATIList:

<ATIType = 00, ATI = NULL>.
29
30
31
32
33
34
Set TransmitATI to
<ATIType = NULL, ATI = NULL>.
Set UATI to NULL.
Set UATIColorCode to NULL.
35
36
22
3GPP2 C.P0087-0 v0.83
Set UATISubnetMask to NULL.
Set SessionSeed to the 32-bit pseudo-random number generated using output of the
pseudo random number generator specified in section 14.5 of [1].
1
2
3
Disable the Address timers.
Set (xo, yo) to (NULL, NULL).
Set CurrentPreRegistrationZoneID to NULL.
4
5
6
If the access terminal receives an Activate command, it shall transition to the Setup State.
4.3.9.2 Access Network Requirements
Upon entering the Inactive State, the access network shall perform the following:
Set the value of the access terminals UATI to NULL.
Set the value of the access terminals UATISubnetMask to NULL.
Set the value of the access terminals UATIColorCode to NULL.
10
11
12
The access network shall transition to the Setup State if it receives a UATIRequest message.
13
4.3.10 Setup State
14
15
In this state, the access terminal sends a request to the access network asking for a UATI and
waits for the access networks response.
16
17
18
Upon entering the Setup State the access terminal shall perform the following:
19
20
21
22
23
Set the TransmitATI to

<ATIType = 11, ATI = SessionSeed>,
Add the following entry to the ReceiveATIList list
<ATIType = 11, ATI = SessionSeed>.
24
SendShall send a UATIRequest message if any of the following conditions are true:.
25
The protocol subtype of the InUse instance of Signaling Adaptation Protocol is equal to
0x0000.
27
There is no InUse instance of Signaling Adaptation Protocol.
28
The protocol subtype of the Signaling Adaptation Protocol is equal to 0x0001 and the
TunnelModeEnabled public data of Signaling Adaptation Protocol is set to '0'.
The protocol subtype of the Signaling Adaptation Protocol is equal to 0x0001 and the
HRPDPreRegistrationAllowed public data of the Overhead Messages Protocol is set to 1.
26
29
30
31
If the TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 1, the

33preregistration zone associated with the UATI and the current preregistration zone are defined
34to be different if following conditions are satisfied:
32
23
3GPP2 C.P0087-0 v0.83
1
2
3
4
If the HRPDPreRegistrationAllowed 8 field of the HRPDPreRegistration record is set to 1 and

the CurrentPreRegistrationZoneID is not equal to HRPDPreRegistrationZoneID field of the
HRPDPreRegistration record and CurrentPreRegistrationZoneID is different from all
HRPDSecondaryPreRegistrationZoneID fields of the HRPDPreRegistration record.
If TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 1, and if

PreRegistrationZone changes:
5
6
7
8
9
10
11
The access terminal shall defer sending of a new UATIRequest until either the
UATIAssignment is received and discarded or UATIResponse timer expires and retry
counter is reset.
The access terminal shall send a new UATIRequest message and restart the UATIResponse
timer.
A valid (see 4.3.8.1.14.2.6.1) UATIAssignment message that satisfies either of the following
conditions is called a fresh UATIAssignment message:
12
13
18
If the protocol subtype of the InUse instance of Signaling Adaptation Protocol is equal to
0x0000, or if there is no InUse instance of Signaling Adaptation Protocol, or if the protocol
subtype of the Signaling Adaptation Protocol is equal to 0x0001 and the
TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 0, and either of
the following conditions are satisfied:
19
OverheadParametersUpToDate, provided as the public data of the Overhead Messages

Protocol, is equal to 1 and the UATIColorCode field in the message matches the
ColorCode, given as public data of the Overhead Messages Protocol, or
the The SubnetIncluded field of the message is equal to 1,
14
15
16
17
20
21
22
25
0x0001 and the TunnelModeEnabled public data of Signaling Adaptation Protocol is set to
1 and both of the following conditions are satisfied:
26

ColorCode, given as public data of the Overhead Messages Protocol, and
The SubnetIncluded field of the message is equal to 1.
23
24
27
28
29
The access terminal shall discard a UATIAssignment message that is not fresh.
30
If TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 0, and if the

32access terminal does not receive a fresh UATIAssignment message within T ADMPATResponse
33seconds
after
transmitting
UATIRequest
message,
e.g.,
after
receiving
an
34AccessChannelMAC.TxEnded indication, it shall return a Failed indication and transition to
35the Inactive State.
31
8 It is assumed that for the intial release of E-UTRAN-HRPD interworking, operators will ensure that
4HRPDPreregistrationZoneIDs
5HRPDPreregistrationAllowed
6procedures
will
not
be
reused
around
areas
within
E-UTRAN
where
is set to 0. In later releases if there is a need to introduce MaxNoMonitor
within E-UTRAN, a solution will need to be developed.
24
3GPP2 C.P0087-0 v0.83

2access terminal does not receive a fresh UATIAssignment message within T ADMPATResponse
3seconds after transmitting UATIRequest message, the access terminal shall retry until a total of
4TADMPATRetry UATIRequest messages have been transmitted. If the timer expires for the final retry,
5it shall return a Failed indication and transition to the Inactive State.
1
If TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 1, and upon

7receiving a fresh UATIAssignment message, if the UATIAssignment is received in response to
8a UATIRequest message (i.e. T ADMPATResponse is active) while in a PreRegistrationZone which is
9different from PreRegistrationZone in which the UATIRequest message was sent, the
10UATIAssignment message shall be discarded.
6
If the access terminal receives a fresh UATIAssignment message then the access terminal
11
Set the UATIColorCode to the UATIColorCode given in the message.
14
Set its UATI and UATISubnetMask as follows:
15
If the message includes the UATI104 field and UATISubnetMask field, the access
terminal shall set its UATI to UATI104 | UATI024 and UATISubnetMask to
UATISubnetMask field included in the message.
Otherwise, the access terminal shall set its UATI to (SectorID[127:24] | UATI024) and
UATISubnetMask to SubnetMask where SectorID and SubnetMask are provided as
public data of Overhead Messages Protocol.
13
16
17
18
19
20
21
22
23
If TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 1, set

CurrentPreRegistrationZoneID
to
HRPDPreRegistrationZoneID
field
of
the
HRPDPreRegistration record.
Delete any entry in the ReceiveATIList list whose ATIType is equal to 11 (i.e., RATI).

<ATIType=10, ATI = (UATIColorCode | UATI[23:0])>.
24
25
26
27
28

Return an Opened indication.
Return a UATIAssigned indication.
Send a UATIComplete message.
29
30
31
32
33
When the access network sends a UATIAssignment message, it shall perform the following:
34
35
36
Access network shall assign a Unicast Access Terminal Identifier (UATI) to the access
terminal for the session as follows:
25
3GPP2 C.P0087-0 v0.83
If the protocol subtype of the InUse instance of Signaling Adaptation Protocol is equal
to 0x0000, or if there is no InUse instance of Signaling Adaptation Protocol, or if the
protocol subtype of the Signaling Adaptation Protocol is equal to 0x0001 and
TunnelModeEnabled public data of the Signaling Adaptation Protocol is set to 0,
Access network may include both UATI104 and UATISubnetMask fields in the
Access network may omit the UATI104 and UATISubnetMask fields from the
message. In this case, the UATI[127:24] is implicitly assigned to be equal to
SectorID[127:24] and UATISubnetMask is implicitly assigned to be SubnetMask,
where SectorID and SubnetMask correspond to the sector that has received the
UATIRequest message.
2
3
6
7
8
9
10
11
12
13
If TunnelModeEnabled public data of the Signaling Adaptation Protocol is set to 1,
Access network shall include both UATI104 and UATISubnetMask fields in the
Access network shall include the UATIColorCode 9 in UATIAssignment message.
14
15
When the access network receives the corresponding UATIComplete message with the
17MessageSequence field of the UATIAssignment message sent, it shall perform the following:
16
Return Opened indication.
Return UATIAssigned indication.
Transition to Open State.
18
19
20
If the access network does not receive the corresponding UATIComplete message in response to
the UATIAssignment message, it may re-transmit the UATIAssignment message. If the access
23network does not receive the UATIComplete message after an implementation specific number
24of re-transmissions of the UATIAssignment message, it shall return a Failed indication and
25transition to the Inactive State.
21
22
4.3.11 Open State
26
27
In this state the access terminal has been assigned a UATI.
28
29
32subtype of the Signaling Adaptation Protocol is equal to 0x0001 and the TunnelModeEnabled
33public data of Signaling Adaptation Protocol is set to 0, the subnet associated with the UATI
30
31
9 The UATIColorCode may be set to the color code associated with the SectorID received over the S101 [6]
4tunnel.
This will reduce probability of color code mismatch when UE performs Idle Handover from
5EUTRAN
to HRPD.
26
3GPP2 C.P0087-0 v0.83
and the current subnet are defined to be different if either of the following two conditions are
2satisfied:
1
The UATISubnetMask is not equal to the SubnetMask of the sector in the active set, or
The result of bitwise logical AND of the UATI and its subnet mask specified by
UATISubnetMask is different from the result of bitwise logical AND of SectorID and its
subnet mask specified by SubnetMask (where SectorID and SubnetMask correspond to the
sector in the active set).
3
4
5
6
7
If the TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 1, the

9PreRegistrationZone associated with the UATI and the current PreRegistrationZone are defined
10to be different if following conditions are satisfied:
8
11
12
13
14
If the HRPDPreRegistrationAllowed 10 field of the HRPDPreRegistration record is set to 1 and

the CurrentPreRegistrationZoneID is not equal to HRPDPreRegistrationZoneID field of the
HRPDPreRegistration record and CurrentPreRegistrationZoneID is different from all
HRPDSecondaryPreRegistrationZoneID fields of the HRPDPreRegistration record.
If the TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 0 and if the
access
terminal
receives
a
RouteUpdate.IdleHO
indication
or
a
17ConnectedState.ConnectionClosed,
and then it receives an OverheadMessages.Updated
18indication, and if both all of the following two conditions are true, then the access terminal
19shall set OldUATI to UATI and shall send a UATIRequest message:
15
16
20
21
22
23
the protocol subtype of the InUse instance of Signaling Adaptation Protocol is equal to
0x0000, or there is no InUse instance of Signaling Adaptation Protocol, or the protocol
TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 0, and
The subnet associated with UATI and the current subnet are different, and
SupportSecondaryColorCodes is set to 0x00 or UATIColorCode is different from all of the

SecondaryColorCode values provided as public data by the Overhead Messages Protocol 11.
24
25
26
If the access terminal receives a SignalingAdaptation.IdleHandoff indication and then it

receives an OverheadMessages.Updated indication, the access terminal shall perform the
29following:
27
28
31
If both of the following two conditions are true, then the access terminal shall set OldUATI
to UATI and shall send a UATIRequest message:
32
30
The subnet associated with UATI and the current subnet are different, and
10 It is assumed that for the intial release of E-UTRAN-HRPD interworking, operators will ensure that
3HRPDPreregistrationZoneIDs
4HRPDPreregistrationAllowed
5procedures
will
not
be
reused
around
areas
within
E-UTRAN
where
is set to 0. In later releases if there is a need to introduce MaxNoMonitor
within E-UTRAN, a solution will need to be developed.
11 The advertisement of SecondaryColorCode values might require the access network to deliver pages
7across
8in
9beyond
10
subnet boundaries into areas in other subnets with the same ColorCode value that is advertised
the SecondaryColorCode values. The means by which the access network accomplishes this are
the scope of this specification.
27
3GPP2 C.P0087-0 v0.83
2
3
SupportSecondaryColorCodes is set to 0x00 or UATIColorCode is different from all of

the SecondaryColorCode values provided as public data by the Overhead Messages
Protocol.
OtherwiseElse, the access terminal shall:
6
7
If InterRATMobilityEnabled is set to 0x01, the access terminal shall transmit an

InterRATMobilityIndication message. Otherwise if InterRATMobilityEnabled is set to
0x00 it shall issue an AirLinkManagement.OpenConnection command.
Upon sending an InterRATMobilityIndication message, the access terminal shall start a

9InterRATMobilityAck
timer with a timeout value of T ADMPIRMA after receiving an
10AccessChannelMAC.TXEnded indication.
8
If the InterRATMobilityIndication timer expires without receipt of an InterRATMobilityAck

12message, the access terminal shall retry until a total of N ADMPIRMI InterRATMobilityIndication
13messages have been transmitted. If the timer expires for the final retry, the access terminal
14shall return a Failed indication and transition to the Inactive State.
11
If the TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 1 and if the
access terminal receives an OverheadMessages.Updated indicationa new HRPDPreRegistration
12
17record , and the protocol subtype of the InUse instance of Signaling Adaptation Protocol is
18equal to 0x0001 and the TunnelModeEnabled public data of Signaling Adaptation Protocol is
19set to 1, then the access terminal shall perform the followingif the following condition is true,
20the access terminal shall set the OldUATI to UATI, shall send a UATIRequest message and
21issue a PreRegistrationZoneChanged indication:
15
16
22
23
Set (xo, yo) to (NULL, NULL).If the PreRegistrationZone associated with the UATI and the
current PreRegistrationZone are different.
26
If HRPDPreRegistrationAllowed, given as public data of the Overhead Messages Protocol,

changes from 0 to 1, then the access terminal should return a Failed indication and
transition to the Inactive State if all of the following conditions are true:
27
UATIColorCode is not equal to the ColorCode, given as public data of the Overhead
Messages Protocol, and
SupportSecondaryColorCode is set to 0x00 or UATIColorCode is different from all of the

SecondaryColorCode values provided as public data by the Overhead Messages
Protocol.
24
25
28
29
30
31
33
If the UATIColorCode is different from ColorCode, given as public data of the Overhead
Messages Protocol, then:
34
35
32
36
37
38
The access terminal shall return a PreRegistrationZoneChanged indication.

If SupportSecondaryColorCode is set to 0x00 or UATIColorCode is different from all of
the SecondaryColorCode values provided as public data by the Overhead Messages
Protocol, then the access terminal shall perform the following after Signaling
Adaptation Protocol has transitioned to Close state:
12 The process by which the E-UTRAN protocol within the access terminal communicates this record to
4the
Address Management Protocol is left to the access terminal implementation
28
3GPP2 C.P0087-0 v0.83
Set the OldUATI to UATI,
Send a UATIRequest message.
If the access terminal receives an UpdateUATI command, it shall process the command as
4specified in 4.3.8.
3
A valid (see 4.3.8.1.14.2.6.1) UATIAssignment message that satisfies either of the following
conditions is called a fresh UATIAssignment message:
5
6
11
TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 0, and either of
the following conditions are satisfied:
12

ColorCode, given as public data of the Overhead Messages Protocol, or
The SubnetIncluded field of the message equal to 1.
7
8
9
10
13
14
15
18
0x0001 and if the TunnelModeEnabled public data of Signaling Adaptation Protocol is set
to 1 and both of the following conditions are satisfied:
19

ColorCode, given as public data of the Overhead Messages Protocol, and
The SubnetIncluded field of the message equal to 1.
16
17
20
21
22
The access terminal shall discard a UATIAssignment message that is not fresh.
23
Upon sending a UATIRequest message, the access terminal shall start a UATIResponse timer
25with a timeout value of TADMPATResponse seconds after the message is transmitted, e.g., after
26receiving an AccessChannelMAC.TxEnded indication if the TunnelModeEnabled public data of
27Signaling Adaptation Protocol is set to 0.
24
Upon sending a UATIRequest message, the access terminal shall start a UATIResponse timer
with a timeout value of TADMPATResponse seconds after the message is transmitted, if the
30TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 1.
28
29

PreRegistrationZone changes after sending a UATIRequest message and the UATIResponse
33timer is active:
31
32
34
35
36
37
38
The access terminal shall defer sending of a new UATIRequest until either the
UATIAssignment is received and discarded or UATIResponse timer expires and retry
counter is reset.
Upon discarding the UATIAssignment message, the access terminal shall send a new
UATIRequest message and restart the UATIResponse timer.
The access terminal shall disable this timer if either of the following conditions is true:
39
29
3GPP2 C.P0087-0 v0.83
1
2
3
4
5
The UATISubnetMask is equal to the SubnetMask of the sector in the active set, and the
result of bitwise logical AND of the UATI and its subnet mask specified by UATISubnetMask
is the same as the result of bitwise logical AND of SectorID and its subnet mask specified
by SubnetMask (where SectorID and SubnetMask correspond to the sector in the active
set), or
The access terminal receives a fresh UATIAssignment message.

8UATIResponse timer expires, the access terminal shall return a Failed indication and
7

11UATIResponse timer expires, the access terminal shall retry until a total of T ADMPATRetry
12UATIRequest messages have been transmitted. If the timer expires for the final retry, it shall
13return a Failed indication and transition to the Inactive State.
10
If the access terminal receives a fresh UATIAssignment message then the access terminal
14
15
Set the UATIColorCode to the UATIColorCode given in the message.
17
Set its UATI and UATISubnetMask as follows:
18
If the message includes the UATI104 field and UATISubnetMask field, the access
terminal shall set its UATI to UATI104 | UATI024 and UATISubnetMask to
UATISubnetMask field included in the message.
Otherwise, the access terminal shall set its UATI to (SectorID[127:24] | UATI024) and
UATISubnetMask to SubnetMask where SectorID and SubnetMask are provided as
public data of Overhead Messages Protocol.
16
19
20
21
22
23
24
25
26
27
28
29
30
If TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 1, set

CurrentPreRegistrationZoneID
to
field
of
the
HRPDPreRegistration record
<ATIType = 10, ATI = (UATIColorCode | UATI[23:0])>.
Return a UATIAssigned indication.
Send a UATIComplete message.
Reset and start an Address timer with a timeout value of T ADMPAddress for the added entry to
the ReceiveATIList.
31
32
33
34
The access terminal shall perform the following when an Address timer corresponding to an
entry in the ReceiveATIList expires:
35
36
37
Disable the Address timer for that entry.
30
3GPP2 C.P0087-0 v0.83
1
2
3
Delete all the entries in the ReceiveATIList that are older than the entry whose Address
timer has expired. An entry X in the list is considered older than another entry Y, if the
entry X has been added to the list prior to the entry Y.
If any of the following conditions are true,
5
6
8
9
the protocol subtype of the InUse instance of Signaling Adaptation Protocol is equal to
0x0000, or
there is no InUse instance of Signaling Adaptation Protocol, or
the protocol subtype of the Signaling Adaptation Protocol is equal to 0x0001 and If
TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 0,
and if the access terminal receives an InitializationState.NetworkAcquired indication followed by

11an OverheadMessages.Updated indication, then the access terminal shall perform the
12following:
10
13
14
15
The access terminal shall create a ReducedSubnetMask by appending (128 UATISubnetMask

+
ReducedSubnetMaskOffset)
0s
to
(UATISubnetMask
ReducedSubnetMaskOffset) 1s.
17
If any of the following conditions is true, then the access terminal shall return a Failed
indication and transition to the Inactive State:
18
The UATISubnetMask is not equal to the SubnetMask of the sector in the active set, or
19
The result of bitwise logical AND of the UATI and ReducedSubnetMask is different from
the result of bitwise logical AND of SectorID and ReducedSubnetMask (where SectorID
and SubnetMask correspond to the sector in the active set).
16
20
21
Upon
receiving
an
InitializationState.NetworkAcquired
indication
followed by an
OverheadMessages.Updated indication and if the protocol subtype of the InUse instance of
24Signaling Adaptation Protocol is equal to 0x0001 and TunnelModeEnabled, provided as public
25data of Signaling Adaptation Protocol, is set to 1, then:
22
23
27
If all of the following conditions are true, then the access terminal shall return a Failed
indication and transition to the Inactive State:
28
UATIColorCode is not equal to the ColorCode, given as public data of the Overhead
Messages Protocol, andTunnelModeEnabled, provided as public data of Signaling
Adaptation Protocol is set to 1,
SupportSecondaryColorCode is set to 0x00 or UATIColorCode is different from all of the

SecondaryColorCode values provided as public data by the Overhead Messages
Protocol.The protocol receives an InitializationState.NetworkAcquired indication,
26
29
30
31
32
33
34
35
CurrentPreRegistrationZoneID is not equal to the HRPDPreRegistrationZoneID field of the

HRPDPreRegistration record,
31
3GPP2 C.P0087-0 v0.83
1
2
If all of the following conditions are true, then Otherwise, the access terminal may send a
UATIRequest message13.:
TunnelModeEnabled, provided as public data of Signaling Adaptation Protocol is set to 1,
The protocol receives an InitializationState.NetworkAcquired indication,
CurrentPreRegistrationZoneID is equal to the HRPDPreRegistrationZoneID field of the

HRPDPreRegistration record,
3
4
5
6
Upon receiving an OverheadMessages.Updated indication, and the TunnelModeEnabled public

8data of Signaling Adaptation Protocol is set to 0 the access terminal shall perform the
9following if MaxNoMonitorDistance is not zero:
7
10
11
12
If (x o, yo) is (NULL, NULL), then the access terminal shall set (x o, yo) to (Longitude,
Latitude), where Longitude and Latitude are public data of the Overhead Messages
Protocol.
13
If (xo, yo) is not (NULL, NULL), then the access terminal shall perform the following:
14
The access terminal shall set (x n, yn) to (Longitude, Latitude), where Longitude and
Latitude are public data of the Overhead Messages Protocol.
The access terminal shall compute NoMonitorDistance with an error of no more than
5% of its true value when |yo/14400| is less than 60 and with an error of no more
than 7% of its true value when |yo/14400| is between 60 and 7014 using the
expression
15
16
17
18
19
yo

xn xo cos 180 14400
16
NoMonitorDistance
20
2
y n yo
The access terminal shall set (x o, yo) to (Longitude, Latitude), where Longitude and
Latitude are public data of the Overhead Messages Protocol.
24
The access terminal shall return a Failed indication and transition to the Inactive State
if both of the following conditions are true:
25
the computed value of NoMonitorDistance is greater than MaxNoMonitorDistance,

and
one of the following conditions is true:
21
22
23
26
27
28
29
13
the UATISubnetMask is not equal to the SubnetMask of the sector in the active
set, or
The access terminal may send a UATIRequest using RATI after a power up scenario. The Access
4Terminal
may also use other criteria to determine if it is useful to perform a UATIRequest.
14 x and y are given in units of 1/4 seconds. x /14400 and y /14400 are in units of degrees.
o
o
o
o
32
3GPP2 C.P0087-0 v0.83
1
2
3
4
the result of bitwise logical AND of the UATI and its subnet mask specified by
UATISubnetMask is different from the result of bitwise logical AND of SectorID
and its subnet mask specified by SubnetMask (where SectorID and SubnetMask
correspond to the sector in the active set).
The access network may send a UATIAssignment message at any time in this state. The
7following are some of the possible triggers for sending a UATIAssignment message:
6
Receiving RouteUpdate.ActiveSetUpdated indication,
Receiving an UpdateUATI command,
Receiving a UATIRequest message.
8
9
10
The access network may return a SubnetChanged indication and send a UATIAssignment
message after reception of a RouteUpdate.ActiveSetUpdated indication. The triggers for
13returning a SubnetChanged indication after reception of a RouteUpdate.ActiveSetUpdated
14indication are outside the scope of this specification.
11
12
When the access network sends a UATIAssignment message, it shall perform the following:
15
17
Assign a Unicast Access Terminal Identifier (UATI) to the access terminal for the session
and include it in a UATIAssignment message.
18
If the protocol subtype of the InUse instance of Signaling Adaptation Protocol is equal
to 0x0000, or if there is no InUse instance of Signaling Adaptation Protocol, or if the
protocol subtype of the Signaling Adaptation Protocol is equal to 0x0001 and
TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 0, and if the
UATIAssignment message is sent in response to a UATIRequest message, the access
network may include both UATI104 and UATISubnetMask. If the access network does
not include the UATI104 and UATISubnetMask fields in the message, the UATI[127:24]
is implicitly assigned to be equal to SectorID[127:24], where SectorID corresponds to
the sector that has received the UATIRequest message.
Otherwise, the access network shall include both UATI104 and UATISubnetMask fields
in the UATIAssignment message.
16
19
20
21
22
23
24
25
26
27
28
When the access network receives a UATIComplete message with the MessageSequence field
30that is equal to the MessageSequence field of the UATIAssignment message that it has sent, it
31shall return a UATIAssigned indication.
29
If the access network does not receive the UATIComplete message in response to the
33corresponding UATIAssignment message within a certain time interval that is specified by the
15
34access network , it should re-transmit the UATIAssignment message. If the access network
35does not receive the UATIComplete message after an implementation specific number of re36transmissions of the UATIAssignment message, it shall return a Failed indication and
32
15 The value of this timeout is determined by the access network and specification of the timeout value is
3outside
the scope of this document.
33
3GPP2 C.P0087-0 v0.83
When the access network receives a InterRATMobilityIndication message and if the protocol
2subtype of the InUse instance of Signaling Adaptation Protocol is equal to 0x0001, it shall
3transmit an InterRATMobilityAck message within T ADMPIRMA seconds.
1
4.3.11.2.1 Processing of HRPD Information received via E-UTRAN
When the E-UTRAN protocol within the access terminal selects a new serving cell 16 the protocol
6shall:
5
Set the HRPDPreRegistrationAllowed field of the HRPDPreRegistration record to 0.
4.3.12 Message Formats
4.3.12.1.1 UATIRequest
10
The access terminal sends the UATIRequest message to request that a UATI be assigned or re12assigned to it by the access network.
11
13
Field
Length (bits)
MessageID
TransactionID
MessageID
The access terminal shall set this field to 0x00.
TransactionID
The access terminal shall increment this value for each new UATIRequest
message sent.
14
15
16
17
Channels
Addressing
SLP
AC
unicast
Priority
Best
Effort
10
4.3.12.2 UATIAssignment
18
19
The access network sends the UATIAssignment message to assign or re-assign a UATI to the
access terminal.
20
21
22
16 The process by which the E-UTRAN protocol within the access terminal communicates this event to
4the
Address Management Protocol is left to the access terminal implementation.
34
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
MessageSequence
Reserved1
SubnetIncluded
UATISubnetMask
0 or 8
UATI104
0 or 104
UATIColorCode 17
UATI024
24
UpperOldUATILength
Reserved2
MessageID
The access network shall set this field to 0x01.
MessageSequence
The access network shall set this to 1 higher than the MessageSequence
field of the last UATIAssignment message (modulo 256) that it has sent
to this access terminal.
2
3
4
Reserved1
5
6
SubnetIncluded
7
8
9
UATISubnetMask
10
11
12
13
UATI104
14
15
16
UATIColorCode
17
18
The access network shall set this field to zero. The access terminal shall
ignore this field.
The access network shall set this field to 1 if the UATI104 field and
UATISubnetMask fields are included in this message; otherwise, the
access network shall set this field to 0.
The access network shall omit this field if SubnetIncluded is set to 0. If
included, the access network shall set this field to the number of
consecutive 1's in the subnet mask of the subnet to which the assigned
UATI belongs.
The access network shall omit this field if SubnetIncluded is set to 0. If
included, the access network shall set this field to UATI[127:24] of the
UATI that it is assigning to the access terminal.
UATI Color Code. The access network shall set this field to the Color
Code associated with the subnet to which the UATI belongs.
17 The UATIColorCode may be set to the color code associated with the SectorID received over the S101
4[6]
tunnel. This will reduce probability of color code mismatch when UE performs Idle Handover from
5EUTRAN
to HRPD.
35
3GPP2 C.P0087-0 v0.83
UATI024
The access network shall set this field to UATI[23:0] of the UATI that it is
assigning to the access terminal.
1
2
UpperOldUATILength
3
4
5
Reserved2
6
7
The access network shall set this field to the number of least
significant octets of OldUATI[127:24] that the access terminal is to send
in the UATIComplete message, in the range from 0 to 13, inclusive.
ignore this field.
Channels
CC
FTC
Addressing
unicast
SLP
Best Effort
Priority
10
4.3.12.2.1 UATIComplete
The access terminal sends this message to notify the access network that it has received the
11UATIAssignment message.
10
12
Field
Length (bits)
MessageID
MessageSequence
Reserved
UpperOldUATILength
UpperOldUATI
8
UpperOldUATILength
MessageID
MessageSequence
The access terminal shall set this field to the MessageSequence field of
the UATIAssignment message whose receipt this message is
acknowledging.
13
14
15
16
Reserved
17
18
The access terminal shall set this field to zero. The access network shall
ignore this field.
UpperOldUATILength The access terminal shall set this field to the length of the UpperOldUATI
20
field in octets.
19
UpperOldUATI
21
22
23
24
25
If UpperOldUATILength in the UATIAssignment message whose receipt

this message is acknowledging is not zero and OldUATI is not NULL, the
access
terminal
shall
set
this
field
to
OldUATI[23+UpperOldUATILength8:24]. Otherwise, the access terminal
shall omit this field.
36
3GPP2 C.P0087-0 v0.83
Channels
AC
RTC
Addressing
unicast
SLP
Reliable18
Priority
Best Effort
10
4.3.12.2.2 HardwareIDRequest
The access network uses this message to query the access terminal of its Hardware ID
information.
3
4
Field
Length
(bits)
MessageID
TransactionID
MessageID
TransactionID
The access network shall increment

HardwareIDRequest message sent.
6
7
this
value
for
each
new
Channels
CC
FTC
Addressing
unicast
SLP
Best
Effort
Priority
40
4.3.12.2.3 HardwareIDResponse
The access terminal sends this message in response to the HardwareIDRequest message.
10
11
Field
Length (bits)
MessageID
TransactionID
HardwareIDType
24
HardwareIDLength
HardwareIDValue
8HardwareIDLe
ngth
MessageID
TransactionID
The access terminal shall set this field to the TransactionID field of the
corresponding HardwareIDRequest message.
12
13
14
18 This message is sent reliably when it is sent over the Reverse Traffic Channel.
37
3GPP2 C.P0087-0 v0.83
HardwareIDType The access terminal shall set this field according to Table 4.3.7.2 -3.
Table 4.3.7.2-3. HardwareIDType encoding
HardwareIDType
field value
Meaning
0x010000
Electronic Serial Number (ESN) ; see [9]
0x00ffff
Mobile Equipment Identifier (MEID); see [9].19
0x00NNNN, where
NNNN is in the range
0x0000 to 0xfffe,
inclusive.
See [4]
0xffffff
Null
All other values
Invalid
HardwareIDLength
3
4
5
HardwareIDValue
6
7
8
If HardwareIDType is not set to 0xFFFFFF, the access terminal shall set

this field to the length in octets of the HardwareIDValue field; otherwise
the access terminal shall set this field to 0x00.
The access terminal shall set this field to the unique ID (specified by
HardwareIDType) that has been assigned to the terminal by the
manufacturer.
Channels
AC
RTC
Addressing
unicast
SLP
Reliable 20
Priority
Best
Effort
40
4.3.12.2.4 AttributeUpdateRequest
10
The sender sends an AttributeUpdateRequest message to offer a set of attribute values for a
given attribute.
11
12
13
Field
Length (bits)
MessageID
TransactionID
One or more instances of the following record

AttributeRecord
Attribute dependent
19 If an access terminal has an MEID, it uses this format. See [10].
38
3GPP2 C.P0087-0 v0.83
MessageID
TransactionID
The
sender
shall
increment
this
AttributeUpdateRequest message sent.
2
3
AttributeRecord
4
5
value
for
each
new
The format of this record is specified in section 14.3 of [1]
Channels
FTC
Addressing
RTC
SLP
unicast
Reliable
Priority
40
4.3.12.2.5 AttributeUpdateAccept
The
sender
sends
an
AttributeUpdateAccept
message
in
8AttributeUpdateRequest message to accept the offered attribute values.
response
to
an
Field
Length (bits)
MessageID
TransactionID
MessageID
TransactionID
corresponding AttributeUpdateRequest message.
10
11
12
13
Channels
FTC
Addressing
SLP
RTC
Reliable
Priority
unicast
40
4.3.12.2.6 AttributeUpdateReject
14
The access network sends an AttributeUpdateReject message

AttributeUpdateRequest message to reject the offered attribute values.
15
in
response
to
an
16
17
Field
Length (bits)
MessageID
TransactionID
MessageID
TransactionID
The access network shall set this value to the TransactionID field of the
18
19
20
21
39
3GPP2 C.P0087-0 v0.83
Channels
SLP
FTC
Addressing
Reliable
Priority
unicast
40
4.3.12.3 InterRATMobilityIndication
This section is a subsection under section 7.3.7.2 of [1].
If the protocol subtype of the Signaling Adaptation Protocol is equal to 0x0001, The the access
terminal sends the InterRATMobilityIndication message to notify the access network that it has
5changed its radio access technology.
3
4
Field
Length (bits)
MessageID
MessageID
Channels
SLP
AC
Addressing
unicast
Priority
Best Effort
20
4.3.12.4 InterRATMobilityAck
10
This section is a subsection under section 7.3.7.2 of [1].
11
If the protocol subtype of the Signaling Adaptation Protocol is equal to 0x0001, The the access
network sends the InterRATMobilityAck message to acknowledge receipt of an
14InterRATMobilityIndication message.
12
13
15
Field
Length (bits)
MessageID
MessageID
16
17
Channels
Addressing
SLP
CC
unicast
40
Priority
Best Effort
20
3GPP2 C.P0087-0 v0.83
4.3.12.5 Interface to Other Protocols
4.3.12.5.1 Commands
This protocol does not issue any commands.
4.3.13 Indications
RouteUpdate.IdleHO
RouteUpdate.ActiveSetUpdated
InitializationState.NetworkAcquired
OverheadMessages.Updated
AccessChannelMAC.TxEnded
SignalingAdaptation.IdleHandoff (Access Terminal only)
7
8
9
10
11
12
13
4.3.13.1 Record Formats
14
4.3.13.1.1 HRPDPreRegistration
15
The following HRPD parameters are set to corresponding parameters received over the E17UTRAN overhead information. The process by which the E-UTRAN protocol within the access
18terminal
communicates this record to the protocol is left to the access terminal
19implementation.
16
20
Parameter Field
Length (bits)
HRPDSecondaryPreRegZoneIDCount
HRPDSecondaryPreRegZoneIDCount occurrences of the

following field:
HRPDSecondaryPreRegZoneID
0 or 8
21
If this field is set to 1, the E-UTRAN network supports the HRPD pre24
registration procedure while the access terminal is on E-UTRAN,
25
otherwise this field is set to 0.
22
23
41
3GPP2 C.P0087-0 v0.83
2
If the HRPDPreRegistrationAllowed is set to 1, this field is set to the
3
HRPD pre-registration-zone ID. Otherwise this field is set to NULL.
1
HRPDSecondaryPreRegZoneIDCount
If the HRPDPreRegistrationAllowed is set to 1, this field is set to the
6
number of secondary pre-registration zone ID covering this E-UTRAN
7
sector. Otherwise this field is set to 0.
4
5
HRPDSecondaryPreRegZoneID
If the field HRPDSecondaryPreRegZoneIDCount is included, and not
10
equal to zero, this field is set to the HRPD secondary pre-registration11
zone ID. Otherwise this field is omitted
8
9
12
4.3.14 Configuration Attributes
13
14
Unless specified otherwise, the access terminal and the access network shall not use the
Generic Attribute Update Protocol to update configurable attributes belonging to the Inter17RATDefault
Address
Management
Protocol.
If
the
value
of
the
18SupportGAUPMaxNoMonitorDistance attribute is 0x01, then the access terminal and the
19access network shall support the use of the Generic Attribute Update Protocol to update values
20of the following attributes belonging to the Inter-RATDefault Address Management Protocol:
15
16
21
MaxNoMonitorDistance
If the value of the SupportGAUPMaxNoMonitorDistance attribute is not 0x01, the access

23network shall not include the MaxNoMonitorDistance attribute in an AttributeUpdateRequest
24message.
22
The access terminal shall not send an AttributeUpdateRequest message containing the
26MaxNoMonitorDistance attribute.
25
The configurable simple attributes for this protocol are listed in Table 4.2.8 -1. The access
terminal and access network shall use as defaults the values in Table 4.2.8 -1 that are typed
29in bold italics.
27
28
42
3GPP2 C.P0087-0 v0.83
Table 4.2.8-1. Configurable Values
43
3GPP2 C.P0087-0 v0.83
Attribute
ID
0xff
0xfe
0xfd
0xfc
0xfb
Attribute
MaxNoMonitorDistance
HardwareSeparableFromSessio
n
SupportGAUPMaxNoMonitorDi
stance
ReducedSubnetMaskOffset
SupportSecondaryColorCodes
Values
Meaning
0x0000
The access terminal will not

transition to the Inactive state
based on distance.
0x0001 to
0xffff
Maximum allowed distance

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

from the hardware that is
identified by the HardwareID.
All other
values
Reserved
0x00
Use of Generic Attribute Update

Protocol to update
MaxNoMonitorDistance is not
supported.
0x01

Protocol to update
MaxNoMonitorDistance is
supported.
All other
values
Reserved
0x00
ReducedSubnetMaskOffset is
zero.
0x01
0x10
Difference between the number

of consecutive 1s in the subnet
mask and that in the reduced
subnet mask.
All other
values
Reserved
0x00
Use of secondary color codes is

not supported.
0x01
Use of secondary color codes is

supported.
44
3GPP2 C.P0087-0 v0.83
Attribute
ID
0xfa
Attribute
Values
InterRATMobilityEnabled
Meaning
All other
values
Reserved
0x00
Sending of the
InterRATMobilityIndication is
disabled
0x01
Sending of the
InterRATMobilityIndication is
enabled upon resuming use of
HRPD.
0x02-0xff
Reserved
4.3.15 Protocol Numeric Constants
3
4
Constant
Meaning
Value
NADMPType
Type field for this protocol.
Error:
Reference
source not
foundTabl
e 2.5.4-1
of [1]
NADMPDefaultInterRAT
Subtype field for this protocol
0x00001
TADMPATResponse
Time to receive UATIAssignment after sending

UATIRequest
120
seconds
TADMPAddress
The duration of time that the access terminal

declares an address match if it receives a
message that is addressed using either the old
or the new UATI
180
seconds
TADMPATRetry
Maximum number of attempts for sending an

UATIRequest message.
TADMPIRMA
Time to receive an InterRATMobilityAck after

sending InterRATMobilityIndication.
2.5
seconds
NADMPIRMI
Maximum number of attempts for sending an

InterRATMobilityIndication
4.3.16 Session State Information
The Session State Information record (see 14.8 of [1]) consists of parameter records.
45
3GPP2 C.P0087-0 v0.83
This protocol defines the following parameter records in addition to the configuration
2attributes for this protocol:
1
4.3.16.1 SessionSeed Parameter
3
4
Table 4.3.10.1-4. The Format of the Parameter Record for the SessionSeed Parameter
Field
Length (bits)
ParameterType
Length
SessionSeed
ParameterType
Length
6
7
SessionSeed
8
9
32
This field shall be set to 0x01 for this parameter record.

This field shall be set to the length of this parameter record in units of
octets excluding the Length field.
This field shall be set to the value of the SessionSeed associated with the
access terminals session.
4.3.16.2 MessageSequence Parameter
10
11
12
Table 4.3.10.2-5. The Format of the Parameter Record for the MessageSequence
Parameter
Field
ParameterType
13
Length
14
15
MessageSequence
16
17
Length (bits)
ParameterType
Length
MessageSequence

This field shall be set to the MessageSequence field of the last
UATIAssignment message that was sent by the source access network.
4.3.16.3 HardwareID Parameter
18
The access network may include the HardwareID parameter Session State Information Record
20to indicate the HardwareID received from the access terminal in a HardwareIDResponse
21message (if available). If the value of the HardwareSeparableFromSession attribute is not equal
22to 0x00 or the HardwareID from the access terminal is not available (e.g., if the access network
23has not requested this information from the access terminal), the access network shall omit
24this Session State Information Record.
19
46
3GPP2 C.P0087-0 v0.83
Table 4.3.10.3-6. The Format of the Parameter Record for the HardwareID Parameter
Field
Length (bits)
ParameterType
Length
HardwareIDType
24
HardwareIDLength
HardwareIDValue
ParameterType
Length
HardwareIDType
5
6
7
HardwareIDLength
9
10
HardwareIDValue
11
12
13
8HardwareIDLength
The access network shall set this field to the value of the
HardwareIDType field in the most recent HardwareIDResponse message
received from the access terminal.
HardwareIDLength field in the most recent HardwareIDResponse
message received from the access terminal.
HardwareIDValue field in the most recent HardwareIDResponse message
received from the access terminal.
14
15
47
3GPP2 C.P0087-0 v0.83
No text.
48
5 CONNECTION LAYER
This section contains specification for Inter-RAT Signaling Adaptation Protocol. In addition, it
also contains specifications for Inter-RAT Initialization State Protocol, Inter-RAT Idle State
4Protocol, Inter-RAT Route Update Protocol and Inter-RAT Overhead Messages Protocol. These
5protocols operate with Inter-RAT Signaling Adaptation Protocol.
2
3
[Editor note [open issue]: If the AT is in tunnel mode, and E-UTRAN coverage is lost, the
7procedure for the connection layer protocol is TBD]
6
5.1 Inter-RAT Signaling Adaptation Protocol
5.1.1 Overview
The Inter-RAT Signaling Adaptation Protocol provides the following functions:
10
11
12
13
14
15
16
17
18
19
20
When instantiated, it keeps record of which air interface (HRPD or E-UTRANnon-HRPD) the
access terminal is currently receiving service in.
When requested by upper layer protocols, it provides a virtual connection service between
the access terminal and the access network over a non-HRPD radio access technology the
E-UTRAN tunnel when the access terminal is receiving service in a non-HRPD radio access
technologyE-UTRAN.
Provides encapsulation of HRPD packets when sent over a non-HRPD radio access
technologythe E-UTRAN tunnel.
Triggers idle and active handoffs from a non-HRPD radio access technologyE-UTRAN to
HRPD access networks based on triggers provided by E-UTRAN.
This protocol allows the creation and removal of a virtual connection between the access
terminal and the access network. The virtual connection can be in one of the following states:
21
22
23
Close State: The virtual connection does not exist.
24
Setup State: The virtual connection setup is in progress.
25
Open State: In this state the virtual connection is open.
Figure 5.1.1-1 provides an overview of the access terminal states and state transitions.
26
3GPP2 C.P0087-0 v0.83
Initial State
Tx AlternateLinkOpenReq
Close
State
Rx AlternateLinkOpenConf
Setup
State
Open
State
Rx AlternateLinkOpenFail
Rx AlternateLinkCloseReq or
Rx AlternateLinkCloseConf
1
2
Figure 5.1.1-1. Inter-RAT Signaling Adaptation Protocol State Diagram (Access Terminal)
Figure 5.1.1-2 provides an overview of the access network states and state transitions.
Initial State
Rx AlternateLinkOpenReq
Close
State
Tx AlternateLinkOpenConf
Setup
State
Open
State
Tx AlternateLinkOpenFail
Rx AlternateLinkCloseReq or
Rx AlternateLinkCloseConf
4
5
Figure 5.1.1-2 Inter-RAT Signaling Adaptation Protocol State Diagram (Access Network)
5.1.2.1 Commands
This protocol defines the following commands:
ActiveHandoffRequest
10
IdleHandoffRequest
11
OpenConnection
12
CloseConnection
3GPP2 C.P0087-0 v0.83
This protocol returns the following indications
ConnectionOpened
ConnectionInitiated
ConnectionClosed
ConnectionFailed
IdleHandoff
LinkAcquired
5.1.2.3 Public Data
This protocol makes the following data public
10
11
Subtype for this protocol.
12
TunnelModeEnabled
13
The Protocol Data Unit for this protocol is a Signaling Adaptation packet.
14
If TunnelModeEnabled is set to 0
15
18
A Signaling Adaptation packet is the same as the packet from the Packet Consolidation
Protocol i.e. Signaling Adaptation Protocol does not add any header to the packet received
from the Packet Consolidation Protocol.
19
All transmitted packets are forwarded to the Security Layer.
20
All received packets are forwarded to the Packet Consolidation Protocol.
16
17
Otherwise,
21
22
23
24
25
26
27
28
A Signaling Adaptation packet is constructed by adding a Signaling Adaptation header

defined in 5.1.6.3 to each packet received from the Packet Consolidation Protocol.
All transmitted Signaling Adaptation packets are forwarded to the non-HRPD radio access
technologyE-UTRAN tunnel.
All Signaling Adaptation packets received from the non-HRPD radio access technologyEUTRAN tunnel are forwarded to the Packet Consolidation Protocol after removing the
Signaling Adaptation header.
This protocol uses the Signaling Application (see section 2 in [1]) to transmit and receive
30messages.
29
3GPP2 C.P0087-0 v0.83
access network shall perform the following in the order specified:
3
4
5
6
7
8
9
10
11
12
that attribute.
13
14
16
17
If the primary RAT is HRPD then the access terminal shall set the TunnelModeEnabled to
0, otherwise it shall set the TunnelModeEnabled to 1.
19
20
The protocol shall enter the Close State.
18
5.1.5 Procedures and Messages for the InConfiguration Protocol Instance of the Protocol
21
5.1.5.1 Procedures
22
This protocol uses the Generic Configuration Protocol (see section 14.7 in [1]) to define the
processing of the configuration messages.
23
24
25
section, in the order specified, when directed by the InUse instance of the Session
26
27
30
31
32
the protocol.
29
33
34
35
36
3GPP2 C.P0087-0 v0.83
instance, then
The access terminal and the access network shall set the initial state of the
InConfiguration protocol instance to the Close State.
Signaling Adaptation Protocol at the access terminal and access network.
4
5
6
InUse protocol.
7
8
10
11
12
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
The
sender
shall
increment
13
14
15
AttributeRecord
16
this
value
for
The format of this record is specified in section 14.3 in [1].
17
Channels
Addressing
FTC
RTC
unicast
18
19
20
SLP
Priority
Reliable
40
each
new
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
2
3
AttributeRecord
4
5
6
7
8

AttributeRecord is given in section 14.3 in [1]. The sender shall not
Channels
FTC
Addressing
SLP
RTC
unicast
Reliable
Priority
40
5.1.6 Procedures and Messages for the InUse Protocol Instance of the Protocol
10
5.1.6.1 Procedures
11
12
5.1.6.1.1.1 OpenConnection
13
When the protocol receives an OpenConnection command:
14
15
If the access terminal is in the Close State,
16
If
TunnelModeEnabled
is
equal
to
0,
AirLinkManagement.OpenConnection command.
If TunnelModeEnabled is equal to 1, then it shall:
17
18
then
it
19
Issue Send an AlternateLinkOpenReq message,
20
Set an AlternateLinkOpenConf timer to TSAPALOpenConf seconds,
21
Transition to the Setup state.
shall
issue
22
23
If the access terminal is in the Open or Setup state it shall ignore this command.
24
If the access network is in the Close State,
If TunelModeEnabled is equal to 2, thenOtherwise it shall ignore this command.
an
3GPP2 C.P0087-0 v0.83
If
TunnelModeEnabled
is
equal
to
0,
If TunnelModeEnabled is equal to 1, then it shall:
2
3
then
Issue Send an AlternateLinkPageReq message,
Set an AlternateLinkOpenReq timer to TSAPALOpenReq seconds,
it
shall
issue
an
Otherwise it shall ignore this command.
If the access network is in the Open or Setup state it shall ignore this command
5.1.6.1.1.2 CloseConnection
If the protocol receives the CloseConnection command in the Open State or in the Setup State,
11the access terminal or the access network:
10
12
If TunnelModeEnabled is equal to 1, it shall:
13
Issue Send an AlternateLinkCloseReq message,
14
Set an AlternateLinkCloseConf timer to TSAPALCloseConf seconds.
15
Otherwise, it shall issue an AirlinkManagement.CloseConnectionignore this command.
When the protocol receives a CloseConnection command in the Close state, the access terminal
or the access network:
16
17
19
If the TunnelModeEnabled is equal to 1, then it shall issue return a ConnectionClosed

indication.
20
Otherwise, it shall issue an AirLinkManagement.CloseConnectionignore this command.
18
5.1.6.1.1.3 ActiveHandoffRequest
21
The non-HRPDE-UTRAN protocol within the access terminal issues this command when the
23access
terminal performs an active handoff to HRPD. If the protocol receives an
24ActiveHandoffRequest command, then:
22
25
26
27
28
29
If the access terminal is in the Open state it shall transition to the Closed State.
The access terminal shall set the TunnelModeEnabled equal to 2 and it shall issue an
If the access terminal is in the Setup state it shall disable the AlternateLinkOpenConf
timer.
The access network shall ignore this command.
30
5.1.6.1.1.4 IdleHandoffRequest
31
The non-HRPDE-UTRAN protocol within the access terminal issues this command when the
access terminal performs an idle handoff to HRPD. The access terminal shall perform the
34following in the order specified:
32
33
3GPP2 C.P0087-0 v0.83
Set TunnelModeEnabled to 0,
Issue Return an IdleHandoff indication,
3
4
5
6
7
If the InUse instance of Overhead Messages Protocol subtype is equal to 0x0001 21, Issue
issue an OverheadMessages.TunnelDeactivate command.
If the protocol receives the command in the Open or Setup state it shall disable the
AlternateLinkOpenConf timer, issue return a ConnectionClosed indication and transition to
the Close State.
5.1.6.1.2 Close State
In this state the virtual connection between the access terminal and access network is closed.
10
5.1.6.1.2.1 Access Terminal Requirements
11
Upon entering this state the access terminal shall check which radio-access-technology (RAT)
is selected as primary, if the primary RAT is set to HRPD then the access terminal shall set the
14TunnelModeEnabled to 0, otherwise it shall set the TunnelModeEnabled to 1 and issues
15OverheadMessages.Activate command.
12
13
If the protocol receives a RouteUpdate.ConnectionInitiated indication and if TunnelModeEnabled

17is equal to 2, the access terminal shall set the TunnelModeEnabled parameter to 0,.
18Otherwise it shall ignore this indication.
16
19
Set the TunnelModeEnabled parameter to 0,
20
Issue a ConnectionInitiated indication.
If the protocol receives an IdleState.ConnectionOpened indication, the access terminal shall

22issue a ConnectionOpened indication.
21
If the protocol receives an IdleState.ConnectionFailed indication and if TunnelModeEnabled is

set to 2, the access terminal shall set the TunnelModeEnabled parameter equal to 1.:
23
24
26
Set the TunnelModeEnabled parameter equal to 1,
27
Issue a ConnectionFailed indication.
If the protocol receives an IdleState.ConnectionFailed indication and TunnelModeEnabled is not

set to 2, the access terminal shall:
28
29
30
Issue a ConnectionFailed indication.
If the protocol receives a ConnectedState.ConnectionClosed indication, the access terminal

32shall issue a ConnectionClosed indication.
31
If the protocol receives an AlternateLinkPageReq message, the access terminal shall:
33
21
OverheadMessages.TunnelDeactivate
4OverheadMessages
command is not supported in the default subtype of
protocol. The Signaling Adaptation protocol is used with multiple RAT interwoking
5specifications.
3GPP2 C.P0087-0 v0.83
Issue Send an AlternateLinkOpenReq message,
Set an AlternateLinkOpenConf timer to TSAPALOpenConf seconds,
If the protocol receives a ReverseTrafficChannelMAC.LinkAcquired indication, the access

5 terminal
shall issue a LinkAcquired indication.The access terminal should send an
6 AlternateLinkCloseConf message upon receiving an AlternateLinkCloseReq message.
4
5.1.6.1.2.2 Access Network Requirements
Upon entering this state the access network shall set the TunnelModeEnabled to NULL.
If the protocol receives a RouteUpdate.ConnectionInitiated indication and if TunnelModeEnabled

is equal to 2, the access network shall set the TunnelModeEnabled parameter to 0.,
9
10
12
Issue a ConnectionInitiated indication.
13
Set the TunnelModeEnabled parameter to 0.
If the protocol receives an IdleState.ConnectionOpened indication, the access network shall

issue a ConnectionOpened indication.
14
15
If the protocol receives an IdleState.ConnectionFailed indication, the access network shall issue
17a ConnectionFailed indication.
16
If the protocol receives a ConnectedState.ConnectionClosed indication, the access network shall

issue a ConnectionClosed indication.
18
19
If the access network receives an AlternateLinkOpenReq message and if TunnelModeEnabled is

21equal to 1, then it shall transition to the Setup State.
20
If the protocol receives a ReverseTrafficChannelMAC.LinkAcquired indication, the access

network shall issue a LinkAcquired indication.
22
23
If the access network receives a Signaling Adaptation-encapsulated HRPD message from the
25access terminal over the non-HRPD radio access technologyE-UTRAN tunnel, it shall set the
26TunnelModeEnabled parameter to 1.
24
If the access network receives a HRPD air interface message from the access terminal over the
28HRPD air interface, it shall set the TunnelModeEnabled parameter to 0.
27
The access network should send an AlternateLinkCloseConf message upon receiving an

AlternateLinkCloseReq message.
29
30
5.1.6.1.3 Setup State
31
32
Upon entering the Setup State the protocol shall issue a ConnectionInitiated indication.
33
If the access terminal receives an AlternateLinkOpenConf message, the access terminal shall:
34
35
Disable the AlternateLinkOpenConf timer,
3GPP2 C.P0087-0 v0.83
Return a ConnectionInitiated indication.
If the access terminal receives an AlternateLinkOpenFail message, the access terminal shall:
Issue Return a ConnectionFailed indication if TunnelModeEnabled is equal to 1,
If the access terminal receives an AlternateLinkCloseReq message, then it shall:
Send an AlternateLinkCloseConf message,
10
Issue Return a ConnectionClosed indication,
11
If the access terminal receives an AlternateLinkCloseConf message, then it shall:
12
13
Disable the AlternateLinkCloseConf timer,
14
15
If the protocol receives an AlternateLinkPageReq message, the access terminal shall ignore
17 this message.
16
18
19
If the AlternateLinkOpenConf timer expires without

AlternateLinkOpenConf message, the access terminal shall:
the
protocol
receiving
20
Issue Return a ConnectionFailed indication if TunnelModeEnabled is equal to 1,
21
the
If the access terminal receives an AddressManagement.PreRegistrationZoneChanged indication

23 it shall:
22
24
25
26
If the protocol receives an IdleState.ConnectionFailed indication and TunnelModeEnabled is set

to 2, the access terminal shall:
27
28
29
30
Issue a ConnectionFailed indication,
31
If the protocol receives a RouteUpdate.ConnectionInitiated indication and TunnelModeEnabled

33is set to 2, the access terminal shall,
32
34

10
3GPP2 C.P0087-0 v0.83
If the access network entered this state due to receiving an AlternateLinkOpenReq message, it
4
5
If the access network is unable to open the virtual connection, for reasons outside the
scope of this standard, the access network shall:
Send an AlternateLinkOpenFail message,
Issue Return a ConnectionFailed indication,
10
11
12
Issue Return a ConnectionInitiated indication,
13
Send an AlternateLinkOpenConf message,
14
Otherwise it shall perform the following:
15
16
If the access network receives an AlternateLinkOpenReq message, then it shall,
17
Disable the AlternateLinkOpenReq timer,
18
Issue Return a ConnectionInitiated indication,
19
Send an AlternateLinkOpenConf message,
20
22
If the AlternateLinkOpenReq timer expires without

AlternateLinkOpenReq message, the access network shall:
23
Issue Return a ConnectionFailed indication,
24
25
If the access network receives an AlternateLinkCloseReq message, then it shall:
26
27
28
29
If the access network receives an AlternateLinkCloseConf message, then it shall:
30
31
32
21
11
the
protocol
receiving
the
3GPP2 C.P0087-0 v0.83
If the access network receives an HRPD air interface message from the access terminal over
the HRPD air interface, it shall set the TunnelModeEnabled parameter to 0, issue return a
ConnectionClosed indication and transition to the Close State.
If the protocol receives an IdleState.ConnectionFailed indication, the access network shall:
1
2

8is set to 2, the access network shall,
7
10

5.1.6.1.4 Open State
11
The access terminal or the access network shall issue return a LinkAcquired indication and a
13ConnectionOpened indication upon entering this state. The access network shall start an
14AlternateLinkOpenComplete timer to T SAPALOpenComplete seconds upon entering this state. The
15access terminal shall send an AlternateLinkOpenComplete message upon entering this state.
12
If the access terminal or the access network receives an AlternateLinkCloseReq message, then
it shall:
16
17
18
19
20
If the access terminal or the access network receives an AlternateLinkCloseConf message, then
22it shall:
21
23
24
25
26
27
The access terminal and the access network may send an AlternateLinkCloseReq message
after an implementation dependent period of inactivity over the tunnel.
If the access terminal receives an AlternateLinkPageReq message, then it shall return a

29 ConnectionClosed
indication, transition to the Close state and process the received
30 AlternateLinkPageReq message in Close state.
28
Upon receiving an AlternateLinkOpenReq message, the access network shall return a

32 ConnectionClosed indication and transition to the Setup state.If the access terminal receives
33 an AlternateLinkPageReq message, then it shall ignore this message.
31
If the AlternateLinkCloseConf timer expires without receiving the AlternateLinkCloseConf

35message, the access terminal or the access network shall:
34
36
12
3GPP2 C.P0087-0 v0.83
If the access terminal receives an AddressManagement.PreRegistrationZoneChanged indication

3it shall,
2
If
the
access
terminal
receives
an
TunnelModeEnabled is set to 2, the access terminal shall:
indication
and
10

12is set to 2, the access terminal shall:
11
14
15
13
If the access network receives an IdleState.ConnectionFailed indication, the access network

shall:
16
17
18
19

21is set to 2, the access network shall,
20
22
23
If the access network receives an AlternateLinkOpenComplete message, then it shall disable

the AlternateLinkOpenComplete timer.
24
25
If
the
AlternateLinkOpenComplete
timer
expires
27AlternateLinkOPenComplete message, the access network shall:
26
28
Return a ConnectionFailed indication,
29
without
receiving
the
If the access network receives an HRPD air interface message from the access terminal over the
HRPD air interface, it shall set the TunnelModeEnabled parameter to 0, issue return a
32ConnectionClosed indication and transition to the Close State.
30
31
5.1.6.1.5 Processing the ReverseTrafficChannelMAC.OpenLoopParametersIssued indication
33
Upon reception of the ReverseTrafficChannelMAC.OpenLoopParametersIssued indication, the

35access network shall set TunneModeEnabled to 2.
34
13
3GPP2 C.P0087-0 v0.83
All messages are transmitted over E-UTRAN physical channels, and can be sent if an HRPD
3connection is not opencan be sent if the primary RAT is not HRPD. The Channels information
4fields are set to non-Traffic channels matching the direction of the message.
2
5.1.6.2.1 AlternateLinkOpenReq
The access terminal sends the AlternateLinkOpenReq message to request a tunnel connection.
6
7
Field
Length (bits)
MessageID
TransactionID
RequestReason
Reserved
MessageID
TransactionID
The access terminal shall increment

AlternateLinkOpenReq message sent.
9
10
RequestReason
11
12
this
value
for
each
new
The access terminal shall set this field to one of the request reasons as
shown in Table 5.1.6.2 -7.
Table 5.1.6.2-7. Encoding of the RequestReason Field
13
Field value
Description
0x0
Access Terminal Initiated
0x1
Access Network Initiated
All other values are invalid

Reserved
14
15
ignore this field.
16
Channels
Addressing
SLP
AC22
unicast
Priority
Best Effort
40
17
22
For the messages with the Channels information field set to non-Traffic channels (i.e. CC
and/or AC,) these All messages are transmitted over non-HRPD radio access technologyE5UTRAN physical channels, and can be sent when an HRPD connection is not open. The
6Channels information fields are set to non-Traffic channels matching the direction of the
7message.
3
4
14
3GPP2 C.P0087-0 v0.83
5.1.6.2.2 AlternateLinkOpenConf
The access network sends the AlternateLinkOpenConf message to confirm a tunnel

3connection.
2
Field
Length (bits)
MessageID
TransactionID
MessageID
TransactionID
corresponding AlternateLinkOpenReq message.
6
7
8
Channels
SLP
CC
Addressing
unicast
Best Effort
Priority
40
5.1.6.2.3 AlternateLinkOpenFail
The access network sends the AlternateLinkOpenFail message to respond to a tunnel

connection.
10
11
12
Field
Length (bits)
MessageID
TransactionID
MessageID
TransactionID
corresponding AlternateLinkOpenReq message.
13
14
15
16
Channels
SLP
CC
Addressing
unicast
Priority
Best Effort
40
17
5.1.6.2.4 AlternateLinkCloseReq
18
The access terminal or the access network sends the AlternateLinkCloseReq message to close a
20tunnel connection.
19
21
15
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
TransactionID
MessageID
TransactionID
The
sender
shall
increment
this
AlternateLinkCloseReq message sent.
2
3
value
for
each
new
Channels
CC
SLP
AC
Addressing
unicast
Best Effort
Priority
40
5.1.6.2.5 AlternateLinkCloseConf
The access terminal or the access network sends the AlternateLinkCloseConf message to
8confirm the request to close a tunnel connection.
7
Field
Length (bits)
MessageID
TransactionID
MessageID
TransactionID
corresponding AlternateLinkCloseReq message.
10
11
12
13
Channels
CC
SLP
AC
Addressing
unicast
Best Effort
Priority
40
5.1.6.2.6 AlternateLinkPageReq
14
The access network sends the AlternateLinkPagkeReq message to request a tunnel connection.
15
16
Field
Length (bits)
MessageID
MessageID
17
18
16
3GPP2 C.P0087-0 v0.83
Channels
SLP
CC
Addressing
5.1.6.2.7
unicast
Best Effort
Priority
40
AlternateLinkOpenComplete
The access terminal sends the AlternateLinkOpenComplete message to confirm a tunnel

connection.
2
3
4
Field
Length (bits)
MessageID
TransactionID
MessageID
TransactionID
The access terminal shall set this value to the TransactionID field of the
corresponding AlternateLinkOpenConf message.
6
7
8
Channels
RTC
Addressing
unicast
SLP
Reliable
Priority
40
5.1.6.3 Header Format
10
When TunnelModeEnabled is not set to 0, the access terminal and the access network shall
12place the following header in front of each packet received from the Packet Consolidation
13Protocol.
11
14
Field
Length (bits)
SAPState
SessionConfigurationToken
ConnectionLayerFormat
SAPState
15
16
17
0 or 16
1
ATI Record
34
Reserved
54
The sender shall set this field to 1 if the Inter-RAT Signaling Adaptation
Protocol is currently in the Open State, otherwise the sender shall set
this field to 0.
SessionConfigurationToken
If SAP is in the Open State, the access terminal shall omit this field.
18
19
17
3GPP2 C.P0087-0 v0.83
Otherwise, The the access terminal shall set this field to the value of the
SessionConfigurationToken which is public data of the Session
Configuration Protocol. The access network shall omit this field.
1
2
3
ConnectionLayerFormat
The access terminal or the access network shall set this field to 1 if the
6
connection layer packet is Format B; otherwise, it shall set this field to
7
0.
4
5
ATI Record
8
9
10
11
Reserved
12
Access Terminal Identifier Record. The access terminal or the access

network shall set this field to the record specifying the access terminals
ID specified by TransmitATI.ATI and TransmitATI.ATIType. This record is
defined in 14.2 in [1].
The access terminal or the access network shall this field to all zeros.
13
5.1.6.4.1 Commands Sent
14
15
AirLinkManagement.OpenConnection
16
17
18
OverheadMessages.Activate
5.1.6.4.2 Indications
19
20
21
22
23
24
25
AddressManagement.PreRegistrationZoneChanged (Access Terminal Only)
26
27
ReverseTrafficChannelMAC.OpenLoopParametersIssued
28
No configuration attributes are defined for this protocol.
29
30
31
32
18
(Access
Network
Only)
3GPP2 C.P0087-0 v0.83
Constant
Meaning
Value
NSAPType
Type field for this protocol
0x1d
NSAPInterRAT
0x0001
TSAPALCloseConf
Maximum time to wait for the

AlternateLinkCloseConf message
5
seconds
TSAPALOpenConf

AlternateLinkOpenConf message
5
seconds
TSAPALOpenReq

AlternateLinkOpenReq message
5
seconds

AlternateLinkOpenComplete message
5
seconds
TSAPALOpenComple
te
Comments
This protocol does not define any parameter record to be included in a Session State
4Information record (see section 14.8 of [1]).
3
19
3GPP2 C.P0087-0 v0.83
5.2 Inter-RAT Initialization State Protocol
5.2.1 Overview
The Inter-RAT Initialization State Protocol provides the procedures and messages required for
5an access terminal to acquire a serving network.
4
At the access terminal, this protocol operates in one of the following four states:
Inactive State: In this state the protocol waits for an Activate command.
Network Determination State: In this state the access terminal chooses an access network
on which to operate.
10
Pilot Acquisition State: In this state the access terminal acquires a Forward Pilot Channel.
11
12
Synchronization State: In this state the access terminal synchronizes to the Control
Channel cycle, receives the Sync message, and synchronizes to CDMA System Time.
Protocol states and events causing transition between states are shown in Figure 5.2.1 -7.
13
20
3GPP2 C.P0087-0 v0.83
Deactivate triggered transitions not shown
Initial State
Activate
Inactive State
Network
Determination
State
r
d o ge
ire ran
p
ex of
er out
m
i
t ion
is
r ev
pilot timer
network selected
expired
SysTim from E-UTRAN
NetworkAcquired
Synchronization
State
Pilot Acquisition
State
pilot acquired
Initial State
Activate
Network
Determination
State
Inactive State
Sync message OK
or ge
d
re ran
i
p f
ex t o
er ou
pilot timer
tim ion
s
expired
i
v
re
Synchronization
State
network selected
Pilot Acquisition
State
pilot acquired
Figure 5.2.1-7. Inter-RAT Initialization State Protocol State Diagram
5.2.2.1 Commands
Activate (an optional Channel Record can be specified with the command)
Deactivate
HRPDMeasStart
10
HRPDMeasStop
21
3GPP2 C.P0087-0 v0.83
NetworkAcquired
HRPDMeasActivated
HRPDMeasDeactivated
5.2.2.3 Public Data
This protocol makes the following data public:
Selected CDMA Channel
10
CDMA System Time
11
The following fields of the Sync message:
12
MaximumRevision
13
MinimumRevision
14
PilotPN
15
HRPDMeasEnabled
16
The transmission unit of this protocol is a message. This is a control protocol; and, therefore, it
18does not carry payload on behalf of other layers or protocols.
17
19
20
21
22
23
24
25
26
27
28
29
30
31
that attribute.
22
3GPP2 C.P0087-0 v0.83
Upon creation, the InUse instance of this protocol in the access terminal shall perform the
3following:
2
The protocol shall enter the Inactive State.
The access terminal shall set HRPDMeasEnabled to 0.
5.2.5.1 Procedures
10
12
The access terminal shall perform the procedures specified in this section, in the order
14specified, when directed by the InUse instance of the Session Configuration Protocol to execute
15the Commit procedures:
13
16
17
21
If the InUse instance of any of the Connection Layer protocols does not have the same
subtype as the corresponding InConfiguration protocol instance, then the access terminal
shall set the initial state of the InConfiguration and InUse protocol instances of the
Initialization State protocol to the Network Determination State.
22
23
The access terminal shall set the attribute values associated with the InUse instance of
this protocol to the attribute values associated with the InConfiguration instance of
this protocol, and
The access terminal shall purge the InConfiguration instance of the protocol.
18
19
20
24
25
26
28
instance, then the access terminal shall perform the following in the order specified:
29
27
30
31
32
Initialization State Protocol at the access terminal.
All the public data that are not defined by this protocol shall be removed from the list of
public data for the InUse protocol instance.
33
34
35
23
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
The
sender
shall
increment
3
4
AttributeRecord
this
value
for
each
new
The format of this record is specified in 14.3 of [1].
Channels
FTC
Addressing
SLP
RTC
Reliable
Priority
unicast
40
8
9
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
10
11
12
AttributeRecord
13
14
15
16
17
18

AttributeRecord is given in 14.3 of [1]]. The sender shall not include
more than one attribute record with the same attribute identifier.
24
3GPP2 C.P0087-0 v0.83
Channels
Addressing
FTC
RTC
unicast
SLP
Reliable
Priority
40
5.2.6.1 Procedures
The access network shall broadcast the Sync message periodically in a synchronous Control
4Channel capsule. This period should not exceed T ISPSync seconds.
3
The access network need not keep state for this protocol.
The access network shall ignore all commands.
If the protocol receives an Activate command in the Inactive State, the access terminal shall
10transition to the Network Determination State.
9
If the protocol receives this command in any other state, the access terminal shall ignore it.
11
12
If the protocol receives a Deactivate command in the Inactive State, the access terminal shall
14ignore it.
13
If the protocol receives this command in any other state, the access terminal shall transition to
16the Inactive State.
15
5.2.6.1.1.3 HRPDMeasStart
17
If the protocol receives a HRPDMeasStart23 command, the access terminal shall perform the
19following:
18
If the access terminal is in the Network Determination State it shall select a CDMA
Channel from the HRPD neighbor list received.
22
Set the HRPDMeasEnabled parameter to 1.
23
Issue Return an HRPDMeasActivated indication.
20
21
24
5.2.6.1.1.4 HRPDMeasStop
25
If the protocol receives a HRPDMeasStop command, the access terminal shall perform the
27following:
26
23 The E-UTRAN protocol within the access terminal requests measurements of neighboring HRPD cells
3to
the HRPD protocol.
25
3GPP2 C.P0087-0 v0.83
The access terminal shall set the HRPDMeasEnabled parameter to 0.
The access terminal shall issue return an HRPDMeasDeactivated indication.
5.2.6.1.2 Inactive State
In the Inactive State the access terminal waits for the protocol to receive an Activate command.
5.2.6.1.3 Network Determination State
In the Network Determination State the access terminal selects a CDMA Channel (see section
814.1 of [1]). If TunnelModeEnabled public data of Signaling Adaptation Protocol is set to 0, the
9access terminal attempts acquire the access network on that CDMA Channel.
7
If a Channel Record was provided with the Activate command and if the TunnelModeEnabled
11public data of Signaling Adaptation Protocol is set to 0, the access terminal should select the
12system and channel specified by the record.
10
Upon entering this state, if TunnelModeEnabled is set to 1 and HRPDMeasEnabled is set to 0

14the access terminal shall remain in the NetworkDetermination state. Upon entering this state if
15the HRPDMeasEnabled is set to 1, the access terminal shall select a CDMA Channel from the
24
16 from the CDMA network information provided by E-UTRAN HRPD neighbor list received.
13
The specific mechanisms to provision the access terminal with a list of preferred networks and
with the actual algorithm used for network selection are beyond the scope of this specification.
17
18
Upon selecting a CDMA Channel the access terminal shall enter the Pilot Acquisition State.
19
5.2.6.1.4 Pilot Acquisition State
20
Upon entering this state, if TunnelModeEnabled is set to 1 and if the CDMA2000SystemTimeInfo is available from E-UTRAN, the access terminal may transition to the
23Synchronization State.
21
22
In the Pilot Acquisition State the access terminal acquires the Forward Pilot Channel of the
selected CDMA Channel.
24
25
Upon entering the Pilot Acquisition State, the access terminal shall tune to the selected CDMA
27Channel and shall search for the pilot. If the access terminal acquires the pilot, it shall enter
25
28the Synchronization State . If the access terminal fails to acquire the pilot within T ISPPilotAcq
29seconds of entering the Pilot Acquisition State, it shall enter the Network Determination State.
26
24 It is beyond the scope of this standard in specifying how the AT might obtain this information during
4initialization.
25 The Access Terminal Minimum Performance Requirements contains specifications regarding pilot
6acquisition
performance.
26
3GPP2 C.P0087-0 v0.83
5.2.6.1.5 Synchronization State
In the Synchronization State the access terminal completes timing synchronization or acquire
26
3CDMA system time information using HRPDSystemTime .
2
Upon entering this state, the access terminal which wish to perform sync
HRPDSystemTime shall perform the following if the TunnelModeEnabled is set to 1:
with
Set default value for MaximumRevision (max value) and MinimumRevision (0x01)
Retrieve CDMA system time information from HRPDSystemTime.
10
The access terminal shall set the CDMA System time based on HRPDSystemTime
information.
11
Return a NetworkAcquired indication,
12
Enter the Inactive State.
Upon entering this state, if the TunnelModeEnabled is set to 0 or if the TunnelModeEnabled is

set to 1 and the access terminal which wish to receive Sync message, the access terminal
13
14
16
Issue the ControlChannelMAC.Activate command.
21
If the access terminal fails to receive a Sync message within TISPSyncAcq seconds of entering
the Synchronization State, the access terminal shall issue a ControlChannelMAC.Deactivate
command and shall enter the Network Determination State. While attempting to receive the
Sync message, the access terminal shall discard any other messages received on the
Control Channel.
22
When the access terminal receives a Sync message:
23
If the access terminals revision number is not in the range defined by the
MinimumRevision and MaximumRevision fields (inclusive) specified in the message,
the access terminal shall issue a ControlChannelMAC.Deactivate command and enter
the Network Determination State.
Otherwise, the access terminal shall:
17
18
19
20
24
25
26
27
30
+ Set the access terminal time to the time specified in the message; The time specified
in the message is the time applicable 160 ms following the beginning of the Control
Channel Cycle in which the Sync message was received,
31
+ Return a NetworkAcquired indication,
32
+ Enter the Inactive State.
28
29
26 HRPDSystemTime is local parameter of Inter-RAT Initialization State Protocol which is the HRPD
3timing
reference infromation receivedthat derives from the cdma-System Timeparameters from E-
4UTRAN
broadcast element (i.e. SIB8). Please refer to E-UTRAN specification [11] on how UE obtains the
5CDMA
timing reference.
27
3GPP2 C.P0087-0 v0.83
5.2.6.2.1 Sync
The access network broadcasts the Sync message to convey basic network and timing
information.
3
4
5
Field
Length (bits)
MessageID
MaximumRevision
MinimumRevision
PilotPN
SystemTime
37
MessageID
The access network shall set this field to 00.
MaximumRevision
Maximum Air-Interface protocol revision supported by the access

network. The access network shall set this field to the value specified in
1.15 of [1]. This value shall be in the range [0x00, 0xff].
7
8
9
MinimumRevision
10
11
12
PilotPN
13
14
SystemTime
15
16
17
18
Minimum Air-Interface protocol revision supported by the access

network. The access network shall set this field to the value specified in
1.15 of [1]. This value shall be in the range [0x00, MaximumRevision].
Pilot PN Offset. The access network shall set this field to the pilot PN
sequence offset for this sector in units of 64 PN Chips.
The access network shall set this field to the CDMA System Time 160 ms
after the start of the Control Channel Cycle in which this Sync message
is being sent. The CDMA System Time is specified in units of 26.66...
ms.
19
Channels
Addressing
SLP
CCsyn
Priority
broadcast
20
21
22
23
ControlChannelMAC.Activate
24
ControlChannelMAC.Deactivate
28
Best Effort
30
3GPP2 C.P0087-0 v0.83
This protocol does not register to receive any indications.
5
6
Constant
Meaning
Value
NISPType
Table
3.1.212.5.4-1 of
[1]
NISPInterRAT
0x0001
TISPSync
Sync message transmission period
1.28
seconds
TISPPilotAcq
Time to acquire pilot in access terminal
60 seconds
TISPSyncAcq
Time to acquire Sync message in access

terminal
5 seconds
Comments
3 Control
Channel Cycle
9Information record (see section 14.8 of [1]).
8
10
29
3GPP2 C.P0087-0 v0.83
5.3 Inter-RAT Idle State Protocol
5.3.1 Overview
The Inter-RAT Idle State Protocol provides the procedures and messages used by the access
5terminal and the access network when the access terminal has acquired a network and a
6connection is not open.
4
This protocol operates in one of the following five states:
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
Sleep State: In this state the access terminal may shut down part of its subsystems to
conserve power. The access terminal does not monitor the Forward Channel, and the
access network is not allowed to transmit unicast packets to it.
Monitor State: In this state the access terminal monitors the Control Channel, listens for
Page messages and if necessary, updates the parameters received from the Overhead
Messages Protocol. The access network may transmit unicast packets to the access
terminal in this state.
Connection Setup State: In this state the access terminal and the access network set-up a
connection.
Tunnel State: In this state the access terminal stop monitoring the Control Channel. All
communications to the access network are provided by the E-UTRAN tunnel. The access
terminal performs pilot measurement in this substate. When pilot measurement is no
longer required, the access terminal has the option to go into an implementation dependent
power saving mode.
Protocol states and events causing the transition between the states are shown in and Figure
24 5.3.1 -9.
23
30
3GPP2 C.P0087-0 v0.83
1
2
3
Figure 5.3.1-8. Inter-RAT Idle State Protocol State Diagram (Access Terminal)
31
3GPP2 C.P0087-0 v0.83

Initial State
Activate
Inactive State
RouteUpdate.ConnectionOpened
T
or
y
en
nD
o
i
t
n
tio
ec
Connection
Setup State
ec
nn
o
xC
n
on
C
Rx
se
qu
Re
Sleep State
t
es see text
see text
Monitor State
Rx OpenConnection, or
Rx RouteUpdate.ConnectionInitiated, or
Rx ConnectionRequest
1
2
lo
xC
Figure 5.3.1-9. Inter-RAT Idle State Protocol State Diagram (Access Network)
This protocol supports periodic network monitoring by the access terminal, allowing for
significant power savings. The following access terminal operation modes are supported:
3
4
5
6
Continuous operation, in which the access terminal continuously monitors the Control
Channel.
10
Suspended mode operation, in which the access terminal monitors the Control Channel
continuously for a period of time and then proceeds to operate in the slotted mode.
Suspended mode follows operation in the Air-Link Management Protocol Connected State
and allows for quick network-initiated reconnection.
11
Slotted mode operation, in which the access terminal monitors only selected slots.
7
8
9
This protocol supports two types of connection set-ups:
12
13
14
15
16
Normal setup: this procedure is always performed at the initiative of the access terminal 27.
It consists of the access terminal sending a ConnectionRequest message which in turn
causes the lower layers to open the connection. The Connection Setup State contains the
requirements for normal setup.
27 The access network may transmit a Page message to the access terminal directing it to initiate the
4procedure.
32
3GPP2 C.P0087-0 v0.83
1
2
3
4
5
6
7
Fast Connect: this procedure is always performed at the initiative of the access network
and consists of the access network opening the connection directly via a RouteUpdate.Open
command28. Fast Connect eliminates the need for the Page / ConnectionRequest exchange
when the access network has pending data to transmit to an access terminal, and is
especially useful when the access terminal is in suspended mode. Support for Fast
Connect at the access network is optional. Support for Fast Connect at the access terminal
is mandatory. The Monitor State contains the requirements for Fast Connect.
5.3.2.1 Commands
10
11
Activate
12
Deactivate
13
OpenConnection
14
Close
15
16
17
ConnectionOpened
18
ConnectionFailed
5.3.2.3 Public Data
19
20
21
does not carry payload on behalf of other layers or protocols.
22
23
24
25
26
28access network shall perform the following in the order specified:
27
29
30
28 This command triggers a transmission of a TrafficChannelAssignment message based on the last
3RouteUpdate
message received from the access terminal.
33
3GPP2 C.P0087-0 v0.83
1
2
3
4
5
6
that attribute.
5.3.5.1 Procedures
9
11
12
15
16
18
subtype as the corresponding InConfiguration protocol instance, then
19
the access terminal shall set the initial state of the InConfiguration and InUse protocol
instances of the Idle State protocol to the Inactive State.
the access network shall set the initial state of the InConfiguration and InUse protocol
instances of the Idle State protocol to the Sleep State.
17
20
21
22
23
24
the protocol.
25
26
27
28
30
instance, then the access terminal and the access network shall perform the following:
31
29
32
33
34
Idle State Protocol at the access terminal and the access network.
InUse protocol.
34
3GPP2 C.P0087-0 v0.83
3
4
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
The
sender
shall
increment
6
7
AttributeRecord
this
value
for
each
new
Channels
FTC
Addressing
SLP
RTC
Reliable
Priority
unicast
40
10
11
12
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
13
14
15
AttributeRecord
16
17
18
19
20

AttributeRecord is given in 14.3 of [1]. The sender shall not include more
than one attribute record with the same attribute identifier.
35
3GPP2 C.P0087-0 v0.83
Channels
Addressing
FTC
SLP
RTC
unicast
Reliable
Priority
40
5.3.6.1 Procedures
When the protocol receives an Activate command in the Inactive State and TunnelModeEnabled
7public data of Signaling Adaptation Protocol equal to 0:
6
The access terminal shall transition to the Monitor State.
The access network shall transition to the Sleep State29.
When the protocol receives an Activate command in the Inactive State and TunnelModeEnabled
public data of Signaling Adaptation Protocol is equal to 1:
10
11
The access terminal shall transition to the Tunnel State.
The access network shall transition to the Sleep State Error: Reference source not found.
12
13
If the protocol receives this command in any other state it shall be ignored.
14
15
When the protocol receives a Deactivate command in the Inactive State it shall be ignored.
16
When the protocol receives this command in any other state:
17
18
19
The access network shall transition to the Inactive State.
5.3.6.1.1.3 OpenConnection
20
When the protocol receives an OpenConnection command in the Inactive State or the
22Connection Setup State, the command shall be ignored.
21
When the protocol receives this command in the Sleep State:
23
24
25
26
27
The access terminal shall transition to the Monitor state and perform the procedures in
5.3.6.1.2 for sending a ConnectionRequest message.
The access network shall queue the command and execute it when it is in the Monitor
State.
29 Since the transitions happen asynchronously, this requirement guarantees that the access network
4will
not transmit unicast packets to the access terminal over the Control Channel when the access
5terminal
is not monitoring the channel.
36
3GPP2 C.P0087-0 v0.83
When the protocol receives this command in the Monitor State:
2
3
4
5
The access terminal shall

ConnectionRequest message.
perform
the
procedures
in
5.3.6.1.2
for
sending
The access network shall send a Page message to the access terminal and transition to the
Connection Setup State.
When the protocol receives this command in the Tunnel State:
7
8
The access terminal shall set a TunnelConnection timer for T ConnReq seconds, and send a
ConnectionRequest message.
5.3.6.1.1.4 Close
When the protocol receives a Close command in the Inactive State or Tunnel State it shall be
11ignored.
10
When the protocol receives a Close command in any other state:
12
13
The access terminal shall transition to the Monitor State.
14
The access network shall transition to the Sleep State.
5.3.6.1.2 Access Terminal Procedures for Sending a ConnectionRequest Message
15
When procedures in this section are invoked, the access terminal shall perform the following:
16
17
18
19
20
21
Send a ConnectionRequest message,

If an AccessChannelMAC.TransmissionSuccessful indication is received, it shall transition
to the Connection Setup State,
If an AccessChannelMAC.TransmissionFailed indication is received, it shall return a
ConnectionFailed indication.
5.3.6.1.3 T12 and T23 Computation
22
The
access
terminal
shall
compute
T 12
and
T23
when
an
AccessChannelMAC.TransmissionSuccessful indication or a ConnectedState.ConnectionClosed
25indication
is received. The access network shall compute T 12 and T23 when an
26AccessChannelMAC.MACLayerCapsuleReceived indication, a ConnectedState.ConnectionClosed,
27or a RouteUpdate.ConnectionLost indicationis received. The access terminal and the access
28network shall compute T12 and T23 as follows:
23
24
T12 Tc Period1 Tc 256 R mod Period1 Period1 24 WakeCount 1 1 1

29
T23 T12 Period 2 T12 256 R mod Period 2 Period 2 24 WakeCount 2 1 1
where Period1 and Period2 are specified in units of slots, Tc is the current CDMA system time.
30
31
When the protocol is in the Inactive State it waits for an Activate command.
32
37
3GPP2 C.P0087-0 v0.83
If at the access terminal receives an OverheadMessages.Updated indication in this state, then

2the
access terminal shall queue the latest OverheadMessages.Updated indication for
3processing in the Monitor state.
1
If the access terminal receives a SignalingAdaptation.ConnectionOpened indication in this

5state, then the access terminal shall return a ConnectionOpened indication.
4
If the access terminal receives a SignalingAdaptation.ConnectionFailed indication in this state,

then the access terminal shall return a ConnectionFailed indication.
6
7
5.3.6.1.5 Sleep State
When the access terminal is in the Sleep State it may stop monitoring the Control Channel by
issuing the following commands:
9
10
11
OverheadMessages.Deactivate
12
The access terminal may shut down processing resources to reduce power consumption.
13
In order to transmit on the Access Channel in this state, the access terminal shall first
15transition from the Sleep State to the Monitor State. If the access terminal requires opening a
16connection, it shall transition to the Monitor state and perform the procedures in 5.3.6.1.2 for
17sending a ConnectionRequest message.
14
When the access network is in the Sleep State, it is prohibited from sending unicast packets to
the access terminal.
18
19
If the access network receives a ConnectionRequest message, it shall transition to the

21Connection Setup State.
20
If the access terminal advertised a suspend period that is current, the access network may
transition to the Monitor State.
22
23
The access network and the access terminal shall transition from the Sleep State to the
25Monitor State in time to send and receive, respectively, the sub-synchronous capsule or the
26synchronous capsule sent at time T satisfying the following condition:
24
[T+256R] mod Period = Offset,
27
where T is the CDMA System Time in slots, and Offset is public data of the Control Channel
29MAC protocol.
28
R shall be obtained as follows:
30
32
If PreferredControlChannelCycleEnabled is equal to 0, then R is the result of applying the

hash function (see section 14.4 of [1]) using the following parameters:
33
Key = SessionSeed
34
Decorrelate = 6 SessionSeed[11:0]
35
N = Max(Period3/256, 1)
36
where SessionSeed is given as public data of the Address Management Protocol.
31
38
3GPP2 C.P0087-0 v0.83
1
2
If PreferredControlChannelCycleEnabled
PreferredControlChannelCycle.
is
equal
to
1,
then
is
set
to
Period shall be computed as follows:
Period1,
Period Period2,
Period3,
CDMA System Time in slots T12

T12 CDMA System Time in slots T23.
Otherwise
The access network and the access terminal shall compute Periodi according to Table 5.3.6.1.5
-8.
5
6
7
Table 5.3.6.1.5-8. Computation of Periodi from SlotCyclei

SlotCyclei
Periodi
0x00 to 0x06
2SlotCyclei 4 slots
0x07 to 0x1c
2(SlotCyclei 0x7) 768 slots
If the access network receives a SignalingAdaptation.ConnectionOpened indication in this state,

9then the access network shall return a ConnectionOpened indication.
8
If the access network receives a SignalingAdaptation.ConnectionFailed indication in this state,

then the access network shall return a ConnectionFailed indication.
10
11
5.3.6.1.6 Monitor State
12
A paging mask is defined as a periodic interval with period and duty cycle defined by three
associated fields PreMaskDuration, MaskDuration, and PostMaskDuration in the PagingMask
15attribute (see 5.3.7.2.3).
13
14
When the access terminal is in the Monitor State, it shall continuously monitor the Control
Channel if MaskCount is equal to 0x00 or one of the following conditions is true for all
18MaskCount paging masks specified by the PagingMask attribute:
16
17
19
20
21
22
T mod [(PreMaskDuration
PreMaskDuration 4, or
MaskDuration
PostMaskDuration)
4]
<
T mod [(PreMaskDuration + MaskDuration

(PreMaskDuration + MaskDuration) 4,
PostMaskDuration)
4]
where PreMaskDuration, MaskDuration, and PostMaskDuration are parameters of the

PagingMask complex attribute.
23
24
When the access network is in the Monitor State, it may send unicast packets to the access
26terminal. When the access network is in the Monitor State, it should not send unicast packets
27to the access terminal unless one of the following conditions is true for all MaskCount paging
28masks specified by the PagingMask attribute:
25
39
3GPP2 C.P0087-0 v0.83
1
2
3
4
T mod [(PreMaskDuration
PreMaskDuration 4, or
MaskDuration
PostMaskDuration)
4]
<
T mod [(PreMaskDuration + MaskDuration

(PreMaskDuration + MaskDuration) 4.
PostMaskDuration)
4]
Upon entering the Monitor State, the access terminal shall issue the following commands:
The access terminal shall comply with the following requirements when in the Monitor State:
10
11
12
13
14
15
16
17
18
19
20
21
22
23
If the access terminal has queued an OverheadMessages.Updated indication or upon

receiving an OverheadMessages.Updated indication, the access terminal shall tune to the
CDMA Channel selected as specified in 5.3.6.1.6.1.1.
If the access terminal entered Monitor State to receive the synchronous capsule, it shall
monitor the overhead messages as specified in the Inter-RAT Overhead Messages Protocol
(see 5.5).
If the access terminal receives a Page message, it shall perform the procedures in 5.3.6.1.2
for sending a ConnectionRequest message.
If the access terminal requires opening a connection, it shall perform the procedures in
5.3.6.1.2 for sending a ConnectionRequest message.
If the access terminal receives a RouteUpdate.ConnectionInitiated indication it shall
transition to the Connection Setup State30.
Access terminal may transition to the Sleep State if the requirements specified in
5.3.6.1.6.1.2 are satisfied.
5.3.6.1.6.1.1 CDMA Channel Selection
24
The access terminal shall select a CDMA Channel from the list of channels or extended
26channels in the SectorParameters message. If no channels or extended channels are listed, the
27access terminal shall use the channel it is currently monitoring. If one or more channels are
28available, the access terminal shall use a hash function (see section 14.4 of [1]) to compute an
29index into the subset of a subset of advertised CDMA Channels according to the following
30procedures.
25
The access terminal shall create a combined channel list as follows:
31
32
33
34
35
36
If the extended channel list is included in the SectorParameters message, the

terminal shall create a combined channel list by appending each CDMA Channel
extended channel list (in order) to the set of CDMA Channels in the channel list (in
Otherwise, the access terminal shall set the combined channel list to the set of
Channels in the channel list.
30 This requirement provides Fast Connect on the access terminal side.
40
access
in the
order).
CDMA
3GPP2 C.P0087-0 v0.83
1
2
3
4
If the SupportedCDMAChannels public data of the Route Update Protocol lists any
channels, then the access terminal shall remove from the combined channel list all CDMA
Channels that are not supported by the access terminal as indicated by the
SupportedCDMAChannels public data of the Route Update Protocol.
The set, S, of CDMA Channels is determined as follows:
6
7
8
If the AccessHashingChannelMaskIncluded field in the SectorParameters message is not

included or is included and set to 0, the access terminal shall set S to the subset of CDMA
Channels in the combined channel list.
11
If the AccessHashingChannelMaskIncluded field in the SectorParameters message is

included and is set to 1, the access terminal shall set S to the subset of CDMA Channels
in the combined channel list for which:
12
9
10
13
Ni is equal to Nmax, where i is the index of the CDMA Channel in the combined
channel list,
where Nj = bitcount(AccessHashingClassMask [AccessHashingMaskLength:0]
Mj), where Mj is the AccessHashingChannelMask field in the SectorParameters
message corresponding to the jth CDMA Channel in the combined channel list;
14
15
16
18
Nmax is the maximum value of Nk for all k , where k is the index of the CDMA
Channel in the combined channel list; and
19
bitcount(x) is the number of 1 bits in the binary representation of x.
17
The CDMA Channels supported by the access terminal are public data of the Route Update
Protocol. The access terminal shall use the following hash function parameters to obtain the
22index into set S:
20
21
23
Key = SessionSeed
24
Decorrelate = 0
25
N = Number of CDMA Channels in set S
where SessionSeed is provided as public data by the Address Management Protocol.
26
5.3.6.1.6.1.2 Transition to Sleep State
27
The access terminal may transition to the Sleep State if all of the following requirements are
29met:
28
30
One of the following requirements is met:
31
32
33
34
35
36
The access terminal entered the Monitor State to receive the synchronous capsule and
has received a Control Channel synchronous Sleep State capsule in the current Control
Channel Cycle and has determined that the SectorParameters message is up to date
(see 5.5.6.1.4.2). The current Control Channel Cycle is defined to be the Control
Channel Cycle that started at slot T/256 , where T is the current CDMA System Time
in slots.
41
3GPP2 C.P0087-0 v0.83
2
3
4
5
6
7
8
The access terminal entered the Monitor State to receive a sub-synchronous capsule,
and has received the sub-synchronous capsule, or did not receive the sub-synchronous
capsule in the expected slots.
Access terminal received an AccessChannelMAC.TxEnded indication for every

AccessChannelMAC.TxStarted indication it received since entering the Monitor State.31
Access terminal has not advertised a suspend period that is current (see section
8.6.6.1.2.1.1 of [1]). The suspend period is current if the time advertised in the associated
ConnectionClose message is greater than the current CDMA System Time 32.
5.3.6.1.6.2.1 General Requirements
10
11
12
13
14
15
16
17
Access network shall select the CDMA Channel following the same specifications as the
access terminal, see 5.3.6.1.6.1.1.
If the access network receives a ConnectionRequest message, it shall transition to the
Connection Setup State.
If the access network requires opening a connection with the access terminal and does not
use an accelerated procedure to set-up a connection, the access network shall send a Page
message to the access terminal over the Control Channel.
21
Access network may use an accelerated procedure to set-up a connection with the access
terminal by bypassing the paging process. The access network should only use this
procedure if it has a reasonable estimate of the access terminals current location. To setup a connection in an accelerated fashion (Fast Connect) the access network shall:
22
Issue a RouteUpdate.Open command.
23
Transition to the Connection Setup State,

RouteUpdate.ConnectionInitiated indication.
18
19
20
24
25
26
when
the
protocol
receives
Access network shall transition to the Sleep State if the access terminal did not advertise a
suspend period that is current.
If the access network receives a SignalingAdaptation.ConnectionOpened indication in this state,

28then the access network shall return a ConnectionOpened indication.
27
If the access network receives a SignalingAdaptation.ConnectionFailed indication in this state,

then the access network shall return a ConnectionFailed indication.
29
30
5.3.6.1.7 Connection Setup State
31
The access terminal and the access network use the Connection Setup State to perform a
normal connection set-up.
32
33
31 This pairing ensures that the access terminal does not have any outstanding messages waiting for an
4answer.
32 The access terminal monitors the Control Channel continuously during a suspend period thus
6avoiding
the delay in opening access network initiated connections due to the sleep period.
42
3GPP2 C.P0087-0 v0.83
Figure 5.3.6.1.7 -10 illustrates the process of opening a connection between the access
2terminal and the access network when this protocol is used along with the default Route
33
3Update and the default Reverse Traffic Channel MAC protocols .
1
the ConnectionRequest and the RouteUpdate

are bundled in the same Access Channel MAC
Layer packet
ConnectionRequest
RTCAck
Idle State Protocol
Pilot + DRC
RTCMAC
TrafficChannelAssignment
ACMAC
ACMAC
ACAck
RTCMAC
Idle State Protocol
RouteUpdate
TrafficChannelComplete
access terminal
access network
Figure 5.3.6.1.7-10. Connection Setup Exchange
The access terminal shall comply with the following requirements.
Upon entering the Connection Setup State the access terminal shall:
Issue an OverheadMessages.Activate command,
10
Issue a ControlChannelMAC.Activate command,
11
Set a state timer for TIDPATSetup seconds,
13
If the access terminal receives a ConnectionDeny message, the access terminal shall return
a ConnectionFailed indication,
14
If the state timer expires, the access terminal shall return a ConnectionFailed indication,
12
33 The Fast Connect message exchange is identical except for not having the Idle State Protocol
3ConnectionRequest
message and the Route Update Protocol RouteUpdate message.
43
3GPP2 C.P0087-0 v0.83
1
2
If the access terminal receives a RouteUpdate.ConnectionOpened indication, it shall return

a ConnectionOpened indication and transition to the Inactive State.
If the ConnectionRequest message contains one or more preferred CDMA channels, then the
5access network should assign a Traffic Channel on one of the preferred CDMA channels.
4
The access network should deny the connection request if all of the following conditions are
true:
6
7
8
9
10
11
the ConnectionRequest message from the access terminal contains one or more preferred
CDMA channels, and
none of the preferred CDMA channels in the ConnectionRequest message can be used to
assign a Traffic Channel.
If the access network entered this state due to receiving a RouteUpdate.ConnectionInitiated

13indication, it shall perform the following:
12
14
15
16
17
18
Set state timer for TIDPANSetup seconds.

If the protocol receives a RouteUpdate.ConnectionOpened indication, the access network
shall return a ConnectionOpened indication and transition to the Inactive State.
If the state timer expires, the access network shall return a ConnectionFailed indication and
shall transition to the Sleep State.
19
20
21
22
Upon reception of a ConnectionRequest message while in this state or if the access network
entered this state due to reception of a ConnectionRequest message, the access network
25
If the access network denies the connection request, it should send the access terminal
a ConnectionDeny message, shall return a ConnectionFailed indication, and shall
transition to the Sleep State.
26
23
24
27
Set state timer for TIDPANSetup seconds.
28
Issue a RouteUpdate.Open command.
29
If the protocol receives a RouteUpdate.ConnectionOpened indication, the access

network shall return a ConnectionOpened indication and transition to the Inactive
State.
If the state timer expires, the access network shall return a ConnectionFailed
indication and shall transition to the Sleep State.
30
31
32
33
34
35
36
37
If the access network did not enter this state as a result of receiving a ConnectionRequest
message, and if the access network does not receive a ConnectionRequest message within
an implementation dependent time interval, then the access network shall return a
ConnectionFailed indication, and shall transition to the Sleep State.
44
3GPP2 C.P0087-0 v0.83
5.3.6.1.8 Tunnel State
Upon entering the Tunnel State, the access terminal should enable its pilot measurement
3entity if HRPDMeasEnabled is set to 1, otherwise the access terminal should disable its pilot
4measurement entity.
2
When the access terminal is in the Tunnel State it shall stop monitoring the Control Channel
6by issuing the following commands:
5
When the access terminal receives a RouteUpdate.ConnectionInitiated indication and

TunnelModeEnabled, provided as public data of the Signaling Adaptation protocol, is equal to
112,:
9
10
stop the TunnelConnection timer if it is running
send an OverheadMessages.TunnelDeactivate command
transition to the Connection Setup state
12
13
14
When the access terminal receives a SignalingAdaptation.IdleHandoff indication it shall

transition to the Monitor State.
15
16
If the TunnelConnection timer expired or access terminal receives a ConnectionDeny message,

18then the access terminal shall issue return a ConnectionFailed indication.
17
When the access terminal receives an InitializationState.HRPDMeasActivated indication, the

access terminal should enable its pilot measurement entity.
19
20
When the access terminal receives an InitializationState.HRPDMeasDeactivated, the access

22terminal should disable its pilot measurement entity.
21
The access terminal may shut down processing resources to reduce power consumption when
it is not required to provide power measurement for report purposes. 34
23
24
The access terminal shall start monitoring the other radio access technology when
26Measurement Gap ends. The access terminal shall perform measurement when requested by
35
27the other radio technology.
25
If the access terminal receives a SignalingAdaptation.ConnectionOpened indication in this

29state, then the access terminal shall return a ConnectionOpened indication.
28
If the access terminal receives a SignalingAdaptation.ConnectionFailed indication in this state,

then the access terminal shall return a ConnectionFailed indication.
30
31
34 The access terminal provide measurement report based on E-UTRAN measurement configuration as
3defined
in [[11]
35 Definition of Measurement Gap is defined in [11]
45
3GPP2 C.P0087-0 v0.83
5.3.6.2.1 Page
The access network sends the Page message to direct the access terminal to request a
connection.
3
4
5
Field
Length (bits)
MessageID
MessageID
Channels
CCsynSS
SLP
CCsubsyn
Addressing
unicast
Best Effort
Priority
20
5.3.6.2.2 ConnectionRequest
The access terminal sends the ConnectionRequest message to request a connection.
9
10
Field
Length (bits)
MessageID
TransactionID
RequestReason
PreferredChannelCount
PreferredChannelCount occurrences of the following

field:
PreferredChannel
24
Reserved
MessageID
TransactionID
The access terminal shall increment

ConnectionRequest message sent.
11
12
13
RequestReason
14
15
this
value
for
each
new
The access terminal shall set this field to one of the request reasons as
shown in Table 5.3.6.2 .2-9.
46
3GPP2 C.P0087-0 v0.83
Table 5.3.6.2.2-9. Encoding of the RequestReason Field
Field value
Description
0x0
Access Terminal Initiated
0x1
Access Network Initiated
All other values are invalid

PreferredChannelCount
The access terminal shall set this field to the number of occurrences of
the PreferredChannel field in this message.
3
4
PreferredChannel
5
6
7
Reserved
8
9
The access terminal shall set this field to the Channel record
specification for the CDMA channel on which the access terminal prefers
to be assigned a Traffic Channel.
ignore this field.
10
Channels
SLP
AC
Addressing
unicast
Priority
Best Effort
40
5.3.6.2.3 ConnectionDeny
11
The access network sends the ConnectionDeny message to deny a connection.
12
13
Field
Length (bits)
MessageID
TransactionID
DenyReason
Reserved
MessageID
TransactionID
corresponding ConnectionRequest message.
14
15
16
DenyReason
17
18
The access network shall set this field to indicate the reason it is denying
the connection, as shown in Table 5.3.6.2 .3-1.
47
3GPP2 C.P0087-0 v0.83
Table 5.3.6.2.3-1. Encoding of the DenyReason Field
Field value
Description
0x0
General
0x1
Network Busy
0x2
Authentication or billing failure
0x3
Preferred channel not available
All other values are reserved

Reserved
ignore this field.
2
3
4
Channels
SLP
CC
Addressing
unicast
Best Effort
Priority
40
The sender sends an AttributeUpdateRequest message to offer a set of attribute values for a
7given attribute.
6
Field
Length (bits)
MessageID
Protocol dependent
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
The
sender
shall
increment
this
10
11
AttributeRecord
12
value
for
each
new
13
Channels
Addressing
FTC
RTC
SLP
Reliable
Priority
unicast
40
14
The
sender
sends
an
message
in
AttributeUpdateRequest message to accept the offered attribute values.
15
16
48
response
to
an
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
Protocol dependent
TransactionID
MessageID
TransactionID
3
4
5
Channels
FTC
Addressing
RTC
SLP
Reliable
Priority
unicast
40

in
response
to
an
8
9
Field
Length (bits)
MessageID
Protocol dependent
TransactionID
MessageID
TransactionID
10
11
12
13
Channels
SLP
FTC
Addressing
Priority
unicast
14
15
16
17
RouteUpdate.Open (access network only)
18
19
20
21
49
Reliable
40
3GPP2 C.P0087-0 v0.83
RouteUpdate.ConnectionOpened
AccessChannelMAC.TxStarted
AccessChannelMAC.TxEnded
AccessChannelMAC.TransmissionSuccessful
AccessChannelMAC.MACLayerCapsuleReceived
10
AccessChannelMAC.TransmissionFailed
11
12
13
14
InitializationState.HRPDMeasActivated
15
InitializationState.HRPDMeasDeactivated
16
SignalingAdaptation.IdleHandoff
17
18
SignalingAdaptation.ConnectionFailed
19
21Generic Attribute Update Protocol to update configurable attributes belonging to the Inter-RAT
22Idle State Protocol. The access terminal and the access network shall support the use of the
23Generic Attribute Update Protocol to update values of the following attributes belonging to the
24Inter-RAT Idle State Protocol:
20
25
PreferredControlChannelCycle
26
SlottedMode
27
PagingMask
28
AccessHashingClassMask
The access terminal shall not

30AttributeUpdateRequest message.
29
include
the
AccessHashingClassMask
in
an
The access network shall not send an AttributeUpdateRequest message containing the
PreferredControlChannelCycle or the PagingMask attribute.
31
32
50
3GPP2 C.P0087-0 v0.83
If the SmallSlotCycleAllowed attribute is set to 0x00, then the access network and the access
2terminal shall not send an AttributeUpdateRequest message proposing a value of the
3SlotCycle1 field of the SlottedMode attribute that is less than 0x06.
1
5.3.7.1 Simple Attributes
The simple configurable attributes are listed in Table 5.3.7.1 -10. The access network and the
access terminal shall use the default values that are typed in bold italics.
5
6
Table 5.3.7.1-10Configurable Simple Attributes
Attribute
ID
0xff
Attribute
SmallSlotCycleAllowed
Values
Meaning
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
0xfe
AccessHashingClassMa
sk
0x0000

hash to channels with any access
hashing class.
0x0001
to 0xffff

hash to channels with designated access
hashing classes (see 5.3.6.1.6.1.1).
5.3.7.2 Complex Attributes
5.3.7.2.1 PreferredControlChannelCycle Attribute
9
10
51
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
Default
Length
N/A
AttributeID
N/A
One or more of the following attribute value record:

{
ValueID
N/A
PreferredControlChannelCycleEnabled
0 or 15
N/A
Reserved
7 or 0
N/A
}
Length
1
2
Length of the complex attribute in octets. The sender shall set this field
to the length of the complex attribute excluding the Length field.
AttributeID
ValueID
The sender shall set this field to an identifier assigned to this complex
value.
4
5
PreferredControlChannelCycleEnabled
7
The sender shall set this field to 1 if PreferredControlChannelCycle field
8
is included in this attribute; otherwise, the sender shall set this field to
9
0.
6
11
If PreferredControlChannelCycleEnabled is set to 1, the sender shall
12
include this field and set it to specify the Control Channel Cycle in which
13
the access terminal transitions out of the Sleep State (see 5.3.6.1.5) in
14
order to monitor the Control Channel. The sender shall omit this field if
15
PreferredControlChannelCycleEnabled is set to 0.
10
Reserved
16
17
18
The length of this field shall be such that the attribute value record is
octet-aligned. The sender shall set this field to zero. The receiver shall
ignore this field.
5.3.7.2.2 SlottedMode Attribute
19
20
52
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
Default
Length
N/A
AttributeID
N/A

{
ValueID
N/A
SlotCycle1
0x9
SlotCycle2
0x9
SlotCycle3
0x9
WakeCount1
0x0
WakeCount2
0x0
Reserved
N/A
}
Length
1
2
AttributeID
ValueID
value.
4
5
SlotCycle1
6
7
SlotCycle2
8
9
10
SlotCycle3
11
12
13
The sender shall set this field to SlotCycle1. The sender shall not set this
field to more than 0x1c.
The sender shall set this field to SlotCycle2. SlotCycle2 shall be greater
than or equal to SlotCycle1. The sender shall not set this field to more
than 0x1c.
The sender shall set this field to SlotCycle3. SlotCycle3 shall be greater
than or equal to SlotCycle2. The sender shall not set this field to more
than 0x1c.
WakeCount1
The sender shall set this field to WakeCount1.
WakeCount2
The sender shall set this field to WakeCount2. WakeCount2 shall be

greater or equal to than WakeCount1.
14
15
16
Reserved
17
The sender shall set this field to 0. The receiver shall ignore this field.
53
3GPP2 C.P0087-0 v0.83
5.3.7.2.3 PagingMask Attribute
1
2
Field
Length (bits)
Default
Length
N/A
AttributeID
N/A
ValueID
N/A
MaskCount
0x00
One or more of the following record:
MaskCount occurrences of the following four fields:

MaskPurpose
N/A
PreMaskDuration
16
N/A
MaskDuration
16
N/A
PostMaskDuration
16
N/A
Length
3
4
AttributeID
ValueID
value.
6
7
MaskCount
The sender shall set this field to the number of paging masks specified
in this complex attribute.
8
9
MaskPurpose
The sender shall set this field to indicate the purpose of the mask
according to Table 5.3.7.2.3 .3-11.
10
11
12
Table 5.3.7.2.3.3-11. Definition of MaskPurpose Field of a Paging Mask

MaskPurpose Value
0x00
Unspecified purpose.
0x01
The paging mask is associated with monitoring the

cdma2000 1x system (see [9]).
0x02-0xff
PreMaskDuration
13
14
MaskDuration
15
16
Meaning
Specified by [4].
The sender shall set this field to the length of the pre-mask duration in
units of four slots.
The sender shall set this field to the length of the masked duration in
54
3GPP2 C.P0087-0 v0.83
PostMaskDuration
1
2
The sender shall set this field to the length of the post-mask duration in
3
4
Constant
Meaning
Value
NIDPType
Table 3.1.212.5.4-1 of [1]
NIDPInterRAT
0x00020x0003
TIDPATSetup
Maximum access terminal time in the

Connection Setup State
2.5 seconds
TIDPANSetup
Maximum access network time in the

Connection Setup State
1 second
TConnReq
Maximum time to wait for transition to

Connection Setup State when
Connection Request is tunneled
through E-UTRAN
2 seconds
Comments
The Session State Information record (see section 14.8 of [1]) consists of parameter records.
The parameter records for this protocol consist of only the configuration attributes of this
8protocol.
7
55
3GPP2 C.P0087-0 v0.83
5.4 Inter-RAT Route Update Protocol
5.4.1 Overview
The Inter-RAT Route Update Protocol provides the procedures and messages used by the access
5terminal and the access network to keep track of the access terminals approximate location
6and to maintain the radio link as the access terminal moves between the coverage areas of
7different sectors. The Inter-RAT Route Update Protocol also provides procedures used by the
8access terminal when it moves from a different radio access technology to HRPD.
4
This protocol can be in one of four states:
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Idle State: This state corresponds to the Air-Link Management Protocol Idle State. In this
state, the access terminal autonomously maintains the Active Set. RouteUpdate messages
from the access terminal to the access network are based on the distance between the
access terminals current serving sector and the serving sector at the time the access
terminal last sent an update.
Connected State: In this state the access network dictates the access terminals Active Set.
Route update messages from the access terminal to the access network are based on
changing radio link conditions.
Tunnel State: This state is associated only with the access terminal. In this state, the
access terminal autonomously maintains the pilot sets the same manner as in the Idle
State. The pilot measurement results of all the pilots in the neighbor list from the public
data are made public to the other radio access technology. The access terminal only
reports the RouteUpdate message when it issues sends ConnectionRequest message or is
requested by the access network.
Transitions between states are driven by commands received from Connection Layer protocols
and the transmission and reception of the TrafficChannelAssignment message.
25
26
The protocol states, messages and commands causing the transition between the states are
28shown in Figure
5.4.1 -11 and Figure 5.4.1 -12 for the access terminal and the access
29network respectively.
27
56
3GPP2 C.P0087-0 v0.83
1
2
Figure 5.4.1-11. Inter-RAT Route Update Protocol State Diagram (Access Terminal)
4
5
Figure 5.4.1-12. Inter-RAT Route Update Protocol State Diagram (Access Network)
This protocol uses parameters that are provided, as public data by the Overhead Messages
Protocol, configured attributes, or protocol constants.
6
7
Table 5.4.1 -12 lists all of the protocol parameters obtained from the public data of the
9Overhead Messages Protocol.
8
57
3GPP2 C.P0087-0 v0.83
1
2
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
RouteUpdateRadiusOverh
ead
Distance (unless modified by the

RouteUpdateRadiusMultiply and/or
RouteUpdateRadiusAdd attributes) between the serving
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
NeighborChannel
Neighbor Channel Record specifying network type and

frequency
5.4.2.1 Commands
Activate
Deactivate
Open
Close
10
SendRouteUpdate
11
12
13
ConnectionLost (access network only)
14
NetworkLost
15
IdleHO
16
ActiveSetUpdated
17
AssignmentRejected
18
ConnectionInitiated
19
ConnectionOpened
58
3GPP2 C.P0087-0 v0.83
5.4.2.3 Public Data
This protocol shall make the following data public:
Active Set
Pilot PN for every pilot in the Active Set
Information provided by the SofterHandoff field in the TrafficChannelAssignment message

for every pilot in the Active Set
MACIndex for every pilot in the Active Set
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 [kcj note: correct editing error in approved RUP]
14
The transmission unit of this protocol is a message. This is a control protocol and, therefore, it
15
17
18
19
20
21
22
23
24
25
26
27
28
29
that attribute.
30
Upon creation, the InUse instance of this protocol in the access terminal and the access
31
33
34
59
3GPP2 C.P0087-0 v0.83
The protocol shall enter the Inactive State.
5.4.5.1 Procedures
5processing
of the configuration messages. The access terminal should send a
6ConfigurationRequest message containing the SupportedCDMAChannels attribute. If the
7access
terminal
sends
a
ConfigurationRequest
message
containing
the
8SupportedCDMAChannels attribute, then the access terminal shall include in the attribute all
9Band Classes and Band Sub-classes supported by the access terminal.
4
10
11
14
15
17
The value of the following public data of the InUse instance of the protocol shall be set to
the corresponding attribute value of the InConfiguration protocol instance:
18
SupportedCDMAChannels
19
If the InUse instance of the Route Update Protocol has the same subtype as this
protocol instance, but the InUse instance of any other protocol in the Connection Layer
does not have the same subtype as the corresponding InConfiguration protocol
instance, then
The access terminal shall set the initial state of the InConfiguration and InUse protocol
instances of the Route Update protocol to the Inactive State.
The access network shall set the initial state of the InConfiguration and InUse protocol
instances of the Route Update protocol to the Idle State.
the protocol.
16
20
21
22
23
24
25
26
27
28
29
30
31
33
If the InUse instance of all protocols in the Connection Layer have the same subtype as the
corresponding InConfiguration protocol instance, then
34
38
The InUse protocol instance at the access terminal shall perform the procedures
specified in 5.4.6.1.2.1.
60
32
35
36
37
3GPP2 C.P0087-0 v0.83
the protocol.
If the InUse instance of the Route Update Protocol does not have the same subtype as this
protocol instance, then the access terminal and the access network shall perform the
following:
instances of the Route Update protocol to the Inactive State.
instances of the Route Update protocol to the Idle State.
Route Update Protocol at the access terminal and the access network.
3
4
7
8
9
10
11
12
13
All the public data that are not defined by this protocol shall be removed from the list of
public data for the InUse protocol instance.
14
15
16
17
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
The
sender
shall
increment
18
19
20
AttributeRecord
21
this
value
for
22
Channels
Addressing
FTC
RTC
unicast
23
24
25
61
SLP
Priority
Reliable
40
each
new
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
2
3
AttributeRecord
4
5
6
7
8

Channels
Addressing
FTC
RTC
unicast
SLP
Reliable
Priority
40
10
5.4.6.1 Procedures
11
12
13
If the protocol receives an Activate command in the Inactive State and the TunneModeEnabled
15public data being set to 0, the access terminal shall perform the following:
14
16
Issue an AccessChannelMAC.Activate command,
17
Transition to the Idle State.
If the protocol receives an Activate command in the Inactive State and the TunneModeEnabled
public data is set to 1, the access terminal shall perform the following:
18
19
20
Transition to the Tunnel State.
If the protocol receives an Activate command in the Inactive State, the access network shall
21
23
24
If this command is received in any other state, it shall be ignored.
25
62
3GPP2 C.P0087-0 v0.83
If the protocol receives a Deactivate command in the Inactive State, it shall be ignored.
If the protocol receives this command in any other state, the access terminal and the access
4network shall:
3
Issue a ReverseTrafficChannelMAC.Deactivate command,
Issue a ForwardTrafficChannelMAC.Deactivate command,
Issue an AccessChannelMAC.Deactivate command,
5.4.6.1.1.3 Open
If the protocol receives an Open command in the Idle State,
10
11
The access terminal shall ignore it.
12
The access network shall:
13
14
Transmit a TrafficChannelAssignment message as follows:

+
The access network should base the TrafficChannelAssignment message on the last
RouteUpdate message it received from the access terminal.
If the SupportedCDMAChannels attribute contains one or more band classes, then

the access network shall assign a Traffic Channel on a CDMA Channel supported
by the access terminal as indicated by the value of the SupportedCDMAChannels
attribute.
15
16
17
18
19
20
Return a ConnectionInitiated indication,
21
Issue a ReverseTrafficChannelMAC.Activate command,
22
Issue a ForwardTrafficChannelMAC.Activate command,
23
Issue an AccessChannelMAC.Deactivate command,
24
Transition to the Connected State.
If this command is received in any other state it shall be ignored.
25
5.4.6.1.1.4 Close
26
If the protocol receives a Close command in the Connected State the access terminal and the
access network shall:
27
28
29
Issue a ReverseTrafficChannelMAC.Deactivate command,
30
Issue a ForwardTrafficChannelMAC.Deactivate command,
31
32
If this command is received in any other state it shall be ignored.
33
63
3GPP2 C.P0087-0 v0.83
5.4.6.1.2 Pilots and Pilot Sets
The access terminal estimates the strength of the Forward Channel transmitted by each sector
in its neighborhood. This estimate is based on measuring the strength of the Forward Pilot
5Channel (specified by the pilots PN offset and the pilots CDMA Channel), henceforth referred
6to as the pilot.
3
4
When this protocol is in the Connected State, the access terminal uses pilot strengths to
8decide when to generate RouteUpdate messages.
7
When this protocol is in the Idle State, the access terminal uses pilot strengths to decide which
sectors Control Channel it monitors.
9
10
When this protocol is in the Tunnel State, the access terminal maintains the pilot sets and
12reports to the other radio access technology the PilotPN and strengths of all the pilots in the
13neighbor list from the Overhead Messages Protocol public data.
11
The following pilot sets are defined to support the Route Update process 36:
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Active Set: The set of pilots (specified by the pilots PN offset and the pilots CDMA Channel)
associated with the sectors currently serving the access terminal. When a connection is
open, a sector is considered to be serving an access terminal when there is a Forward
Traffic Channel, Reverse Traffic Channel and Reverse Power Control Channel assigned to
the access terminal. When a connection is not open, a sector is considered to be serving
the access terminal when the access terminal is monitoring that sectors control channel.
Candidate Set: The pilots (specified by the pilots PN offset and the pilots CDMA Channel)
that are not in the Active Set, but are received by the access terminal with sufficient
strength to indicate that the sectors transmitting them are good candidates for inclusion in
the Active Set.
Neighbor Set: The set of pilots (specified by the pilots PN offset and the pilots CDMA
Channel) that are not in either one of the two previous sets, but are likely candidates for
inclusion in the Active Set.
Remaining Set: The set of all possible pilots (specified by the pilots PN offset and the pilots
CDMA Channel) on the current channel assignment, excluding the pilots that are in any of
the three previous sets.
At any given instant a pilot in the current CDMA Channel is a member of exactly one set.
31
The access terminal maintains all four sets. The access network maintains only the Active Set.
32
The access terminal complies with the following rules when searching for pilots, estimating the
34strength of a given pilot, and moving pilots between sets.
33
5.4.6.1.2.1 Neighbor Set Search Window Parameters Update
35
The access terminal shall maintain RouteUpdateNeighborList which is a list of structures of

37type Neighbor (defined below). For each pilot (specified by the pilots PN offset and the pilots
36
36 In this context, a pilot identifies a sector.
64
3GPP2 C.P0087-0 v0.83
CDMA Channel) in the Neighbor Set, the access terminal shall maintain a structure in the
2RouteUpdateNeighborList.
1
A Neighbor structure consists of four fields: PilotPN, Channel, SearchWindowSize, and

SearchWindowOffset.
3
4
The RouteUpdateNeighborList is used by the access terminal to perform pilot search on a pilot
6in the Neighbor Set.
5
When this set of procedures is invoked, the access terminal shall perform the following steps in
the order specified:
7
8
11
For each pilot (specified by its pilot PN and its channel) in the Neighbor Set, the access
terminal shall first initialize the corresponding Neighbor structure in
RouteUpdateNeighborList as follows:
12
Set the structures PilotPN field to the neighbor pilots PN.
13
Set the structures Channel field to the neighbor pilots channel record.
14
Set the structures SearchWindowSize

SearchWindowNeighbor.
Set the structures SearchWindowOffset to zero.
9
10
15
16
17
18
19
20
21
22
23
24
field
to
the
configurable
attribute
For each pilot (specified by the pilots PN offset and the pilots CDMA Channel) listed in the
OverheadMessagesNeighborList, the access terminal shall set the non-NULL fields of the
corresponding Neighbor structure in the RouteUpdateNeighborList to the fields of the
Neighbor structure in the OverheadMessagesNeighborList for this pilot.
For each pilot (specified by the pilots PN offset and the pilots CDMA Channel) listed in the
NeighborListMessageNeighborList, the access terminal shall set the non-NULL fields of the
corresponding Neighbor structure in the RouteUpdateNeighborList to the fields of the
Neighbor structure in the NeighborListMessageNeighborList for this pilot.
5.4.6.1.2.2 Pilot Search
25
The access terminal shall continually search for pilots in the Connected State and whenever it
27is monitoring the Control Channel in the Idle State. The access terminal shall search for pilots
28in all pilot sets in the Connected State and Idle State.
26
The access terminal shall continually search for pilots in the Tunnel State. In the Tunnel State,
30the access terminal shall search for pilots in the Active Set, the Candidate Set and the
31Neighbor Set, and may search for the pilots in the Remaining Set.
29
This pilot search shall be governed by the following rules:
32
33
34
35
36
Search Priority: The access terminal should use the same search priority for pilots in the
Active Set and Candidate Set. In descending order of search rate, the access terminal shall
search, most often, the pilots in the Active Set and Candidate Set, then shall search the
pilots in the Neighbor Set, and lastly shall search the pilots in the Remaining Set.
65
3GPP2 C.P0087-0 v0.83
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Search Window Size: The access terminal shall use the search window size specified by the
configurable attribute SearchWindowActive for pilots in the Active Set and Candidate Set.
For each pilot in the Neighbor Set, the access terminal shall use the search window size
specified by Table 5.4.6.2 -16 and SearchWindowSize field of the corresponding Neighbor
structure in the RouteUpdateNeighborList. The access terminal shall use search window
size specified by configurable attribute SearchWindowRemaining for pilots in the
Remaining Set.
Search Window Center: The access terminal should center the search window around the
earliest usable multipath component for pilots in the Active Set. The access terminal
should center the search window for each pilot in the Neighbor Set around the pilots PN
sequence offset plus the search window offset specified by Table 5.4.6.2 -17 and
SearchWindowOffset field of the corresponding Neighbor structure in the
RouteUpdateNeighborList using timing defined by the access terminals time reference (see
section 12.3.1.3.6 of [1]). The access terminal should center the search window around the
pilots PN sequence offset using timing defined by the access terminals time reference (see
section 12.3.1.3.6 of [1]) for the Remaining Set.
5.4.6.1.2.3 Pilot Strength Measurement
17
The access terminal shall measure the strength of every pilot it searches. The strength
estimate formed by the access terminal shall be computed as the sum of the ratios of received
20pilot energy per chip, E c, to total received spectral density, I 0 (signal and noise) for at most k
21multipath components, where k is the maximum number of multipath components that can be
22demodulated simultaneously by the access terminal.
18
19
5.4.6.1.2.4 Pilot Drop Timer Maintenance
23
For each pilot, the access terminal shall maintain a pilot drop timer.
24
If DynamicThresholds is equal to 0, the access terminal shall perform the following:
25
26
27
28
29
30
31
The access terminal shall start a pilot drop timer for each pilot in the Candidate Set or the
Active Set whenever the strength becomes less than the value specified by PilotDrop. The
access terminal shall consider the timer to be expired after the time specified by
PilotDropTimer.
The access terminal shall reset and disable the timer whenever the strength of the pilot
becomes greater than the value specified by PilotDrop.
If DynamicThresholds is equal to 1, the access terminal shall perform the following:
32
33
34
35
36
37
The access terminal shall start a pilot drop timer for each pilot in the Candidate Set
whenever the strength of the pilot becomes less than the value specified by PilotDrop. The
access terminal shall consider the timer value to be expired after the time specified by
PilotDropTimer. The access terminal shall reset and disable the timer if the strength of the
pilot becomes greater than the value specified by PilotDrop.
66
3GPP2 C.P0087-0 v0.83
1
2
3
4
For each pilot in the Active Set, the access terminal shall sort pilots in the Active Set in
order of increasing strengths, i.e., PS1 PS 2 PS 3 ... PS N A , where NA is the number of
the pilots in the Active Set. The access terminal shall start the timer whenever the strength
PSi satisfies the following inequality:
SoftSlope
DropIntercept PilotDrop
10 log10 PS j
,
8
2
2
j i
10 log10PSi max
i = 1, 2, ..., NA 1
The access terminal shall reset and disable the timer whenever the above inequality is
not satisfied for the corresponding pilot.
6
7
Sections 5.4.6.1.2.6 and 5.4.6.1.6.5 specify the actions the access terminal takes when the
pilot drop timer expires.
8
9
5.4.6.1.2.5 Active Set Management
10
The access terminal shall support a maximum Active Set size of NRUPActive pilots.
11
Rules for maintaining the Active Set are specific to each protocol state (see 5.4.6.1.5.1 and
5.4.6.1.6.15.4.6.1.6.3).
12
13
5.4.6.1.2.6 Candidate Set Management
14
The access terminal shall support a maximum Candidate Set size of NRUPCandidate pilots.
15
The access terminal shall add a pilot to the Candidate Set if one of the following conditions is
met:
16
17
18
19
Pilot is not already in the Active Set or Candidate Set and the strength of the pilot exceeds
the value specified by PilotAdd.
21
Pilot is deleted from the Active Set, its pilot drop timer has expired, DynamicThresholds is
equal to 1, and the pilot strength is above the threshold specified by PilotDrop.
22
Pilot is deleted from the Active Set but its pilot drop timer has not expired.
20
The access terminal shall delete a pilot from the Candidate Set if one of the following
24conditions is met:
23
25
Pilot is added to the Active Set.
26
Pilots drop timer has expired.
29
Pilot is added to the Candidate Set; and, as a consequence, the size of the Candidate Set
exceeds NRUPCandidate. In this case, the access terminal shall delete the weakest pilot in the
set. Pilot A is considered weaker than pilot B:
30
If pilot A has an active drop timer but pilot B does not,
31
If both pilots have an active drop timer and pilot As drop timer is closer to expiration
than pilot Bs, or
27
28
32
67
3GPP2 C.P0087-0 v0.83
If neither of the pilots has an active drop timer and pilot As strength is less than pilot
Bs.
5.4.6.1.2.7 Neighbor Set Management
The access terminal shall support a minimum Neighbor Set size of NRUPNeighbor pilots.
5
6
The access terminal shall maintain a counter, AGE, for each pilot in the Neighbor Set as
follows.
The access terminal shall perform the following in the order specified:
8
9
10
11
12
13
If a pilot is added to the Active Set or Candidate Set, it shall be deleted from the Neighbor
Set.
If a pilot is deleted from the Active Set, but not added to the Candidate Set, then it shall be
added to the Neighbor Set with the AGE of 0.
If a pilot is deleted from the Candidate Set, but not added to the Active Set, then it shall be
added to the Neighbor Set with the AGE of 0.
17
If the size of the Neighbor Set is greater than the maximum Neighbor Set supported by the
access terminal, the access terminal shall delete enough pilots from the Neighbor Set such
that the size of the Neighbor Set is the maximum size supported by the access terminal
and pilots with higher AGE are deleted first37.
18
If the access terminal receives an OverheadMessages.Updated indication, then:
19
The access terminal shall increment the AGE for every pilot in the Neighbor Set.
20
22
For each pilot in the neighbor list given as public data by the Overhead Messages
Protocol that is a member of the Neighbor Set, the access terminal shall perform the
following:
23
14
15
16
21
24
27
For each pilot in the neighbor list given as public data by the Overhead Messages
Protocol (in the order specified in the neighbor list) that is a member of the Remaining
Set, the access terminal shall perform the following:
28
25
26
29
30
31
The access terminal shall set the AGE of this neighbor list pilot to the minimum of
its current AGE and NeighborMaxAge.
If the addition of this neighbor list pilot to the Neighbor Set would not cause the
size of the Neighbor Set size to increase beyond the maximum Neighbor Set size
supported by the access terminal, then the access terminal shall add this neighbor
list pilot to the Neighbor Set with its AGE set to NeighborMaxAge.
37 The order in which pilots of the same AGE are deleted does not matter in this case.
68
3GPP2 C.P0087-0 v0.83
If the addition of this neighbor list pilot would cause the size of the Neighbor Set to
increase beyond the maximum Neighbor Set size supported by the access terminal
and the Neighbor Set contains at least one pilot with AGE greater than
NeighborMaxAge associated with the pilots channel, then the access terminal shall
delete the pilot in the Neighbor Set for which the difference between its AGE and the
NeighborMaxAge associated with that pilot's channel (i.e., AGE - NeighborMaxAge)
is the greatest and shall add this neighbor list pilot to the Neighbor Set with its AGE
set to NeighborMaxAge associated with the pilots channel.
and the Neighbor Set does not contain a pilot with AGE greater than
NeighborMaxAge associated with the pilots channel, the access terminal shall not
add this neighbor list pilot to the Neighbor Set.
2
3
4
5
6
7
8
9
10
11
12
13
14
If the access terminal receives a NeighborList message, then:
15
The access terminal shall increment the AGE for every pilot in the Neighbor Set.
16
17
For each pilot in the neighbor list given in the NeighborList message that is a member
of the Neighbor Set, the access terminal shall perform the following:
18
19
22
For each pilot in the neighbor list given in the NeighborList message (in the order
specified in the message) that is a member of the Remaining Set, the access terminal
23
If the addition of this neighbor list pilot to the Neighbor Set would not cause the
size of the Neighbor Set size to increase beyond the maximum Neighbor Set size
supported by the access terminal, then the access terminal shall add this neighbor
list pilot to the Neighbor Set with its AGE set to NeighborMaxAge.
and the Neighbor Set contains at least one pilot with AGE greater than
NeighborMaxAge associated with the pilots channel, then the access terminal shall
delete the pilot in the Neighbor Set for which the difference between its AGE and the
NeighborMaxAge associated with that pilot's channel (i.e., AGE - NeighborMaxAge)
is the greatest and add shall this neighbor list pilot to the Neighbor Set with its AGE
set to NeighborMaxAge associated with the pilots channel.
and the Neighbor Set does not contain a pilot with AGE greater than
NeighborMaxAge associated with the pilots channel, the access terminal shall not
add this neighbor list pilot to the Neighbor Set.
20
21
The access terminal shall set the AGE of this neighbor list pilot to the minimum of
its current AGE and NeighborMaxAge.
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
The access terminal shall perform the procedures specified in 5.4.6.1.2.1 if a pilot (specified by
the pilots PN offset and the pilots CDMA Channel) is added to or deleted from the Neighbor
42Set.
40
41
69
3GPP2 C.P0087-0 v0.83
5.4.6.1.2.8 Remaining Set Management
The access terminal shall initialize the Remaining Set to contain all the pilots whose PN offset
3index is an integer multiple of PilotIncrement and are not already members of any other set.
2
The access terminal shall add a pilot to the Remaining Set if it deletes the pilot from the
Neighbor Set and if the pilot was not added to the Active Set or Candidate Set.
4
5
The access terminal shall delete the pilot from the Remaining Set if it adds it to another set.
5.4.6.1.2.9 Pilot PN Phase Measurement
The access terminal shall measure the arrival time, PILOT_ARRIVAL, for each pilot reported to
the access network. The pilot arrival time shall be the time of occurrence, as measured at the
10access terminal antenna connector, of the earliest arriving usable multipath component of the
11pilot. The arrival time shall be measured relative to the access terminals time reference in
12units of PN chips. The access terminal shall compute the reported pilot PN phase,
13PILOT_PN_PHASE, as:
8
9
14
PILOT_PN_PHASE = (PILOT_ARRIVAL + (64 PILOT_PN)) mod 215,
where PILOT_PN is the PN sequence offset index of the pilot.
15
5.4.6.1.3 Message Sequence Numbers
16
The access network shall validate all received RouteUpdate messages as specified in
5.4.6.1.3.1.
17
18
The access terminal shall validate all received TrafficChannelAssignment messages as

20specified in 5.4.6.1.3.2.
19
The RouteUpdate message and the TrafficChannelAssignment

MessageSequence field that serves to flag duplicate or stale messages.
21
message
carry
independent
of
22
The MessageSequence field of the RouteUpdate message

24MessageSequence field of the TrafficChannelAssignment message.
23
is
the
5.4.6.1.3.1 RouteUpdate Message Validation
25
When the access terminal first sends a RouteUpdate message, it shall set the
27MessageSequence field of the message to zero. Subsequently, the access terminal shall
28increment 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
30valid.
29
The access network shall initialize the receive pointer, V(R) to the MessageSequence field of the
32first RouteUpdate message it received in the Idle State, and the access network shall
33subsequently 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
validate the message using the procedure defined in 14.6 of [1]. The access network shall
36discard the message if it is invalid.
34
35
70
3GPP2 C.P0087-0 v0.83
5.4.6.1.3.2 TrafficChannelAssignment Message Validation
The access network shall set the MessageSequence field of the TrafficChannelAssignment
3message it sends in the Idle State to zero. Subsequently, each time the access network sends a
4new TrafficChannelAssignment message in the Connected State, it shall increment this field. If
5the access network is sending the same message multiple times, it shall not change the value
38
6of this field between transmissions .
2
The access terminal shall initialize the receive pointer, V(R), to the MessageSequence field of
8the TrafficChannelAssignment message that it receives in the Idle State or in the Tunnel State.
7
When the access terminal receives a TrafficChannelAssignment message in the Connected

State, it shall validate the message using the procedure defined in 14.6 of [1]. The access
11terminal shall discard the message if it is invalid.
9
10
5.4.6.1.3.3 AttributeOverride Message Validation
12
The access network shall set the MessageSequence field of the first AttributeOverride message
14that it sends after the Route Update protocol enters the Connected State to zero. Subsequently,
15each time the access network sends a new AttributeOverride message in the Connected State,
16it shall increment this field. If the access network is sending the same message multiple times,
39
17it shall not change the value of this field between transmissions .
13
The access terminal shall initialize the receive pointer, V(R), to the MessageSequence field of
19the first AttributeOverride message that it receives in the Connected State.
18
When the access terminal receives a subsequent AttributeOverride message, it shall validate
the message using the procedure defined in 14.6 of [1]. The access terminal shall discard the
22message if it is invalid.
20
21
23
Upon entering this state, the access terminal shall perform the following:
24
25
26
The access terminal shall set the Active Set, the Candidate Set, and the Neighbor Set to
NULL.
29
The access terminal shall initialize the Remaining Set to contain all the pilots whose PN
offset index is an integer multiple of PilotIncrement and are not already members of any
other set.
30
The access terminal shall perform the following in the order specified:
31
Remove all Neighbor structures from OverheadMessagesNeighborList.
32
Remove all Neighbor structures from NeighborListMessageNeighborList.
33
Perform the procedures specified in 5.4.6.1.2.1.
27
28
34
35
The access terminal shall set (xL,yL), the longitude and latitude of the sector in whose
coverage area the access terminal last sent a RouteUpdate message, to (NULL, NULL).
38 The access network may send a message multiple times to increase its delivery probability.
39 The access network may send a message multiple times to increase its delivery probability.
2
3
71
3GPP2 C.P0087-0 v0.83
If the access terminal receives a SignalingAdaptation.ConnectionInitiated indication in this

2state, then the access terminal shall return a ConnectionInitiated indication.
1
5.4.6.1.5 Idle State
In this state, RouteUpdate messages from the access terminal are based on the distance
5between the sector where the access terminal last sent a RouteUpdate message and the sector
6currently in its active set.
4
The access network sends the TrafficChannelAssignment message to open a connection in this
8state.
If the access network sends a TrafficChannelAssignment message when the
9TunnelModeEnabled public data of the Signaling Adaptation protocol is not set to 0, the order
10of sending related messages with TrafficChannelAssignment is specified in illustrated in Figure
115.4.6.1.5-1.
7
12
13
14
15
16
17
18
19
Remove all Neighbor structures from NeighborListMessageNeighborList and perform the

procedures specified in 5.4.6.1.2.1.
Stop using the parameters specified in the AttributeOverride message in the set
management procedures and start using values specified by the
SetManagementSameChannelParameters and the
SetManagementDifferentChannelParameters attributes whichever applicable, in the set
management procedures.
If the access network issues a TrafficChannelAssignment message when the

TunnelModeEnabled public data of the Signaling Adaptation protocol is not set to 0, the order
22of sending related messages with TrafficChannelAssignment is specified in section [ref].If the
23access terminal receives a SignalingAdaptation.ConnectionInitiated indication in this state, then
24the access terminal shall return a ConnectionInitiated indication.
20
21
Figure 5.4.6.1.5-1 illustrates the connection setup exchange process 40 between the access
26terminal and the access network when the TunnelModeEnabled public data of the Signaling
27Adaptation protocol is not set to 0.
25
28
29
40 It is suggested that the access terminal sends RouteUpdate message with ConnectionRequest
4message.
It is suggested that the access network sends HRPDSilenceParameters message and
5HRPDOpenLoopParameters
message before access network sends TrafficChannelAssignment message.
72
3GPP2 C.P0087-0 v0.83
1
2
Figure 5.4.6.1.5-1. Connection Setup Exchange for inter-RAT tunneling mode
5.4.6.1.5.1 Active Set Maintenance
The access network shall not initially maintain an Active Set for the access terminal in this
6state.
5
If the access network receives an Open command, prior to send a TrafficChannelAssignment

message, the access network shall initialize the Active Set to the set of pilots in the
9TrafficChannelAssignment message that it sends in response to command (see 5.4.6.1.1.3).
7
8
The access terminal shall initially keep an Active Set of size one when it is in the Idle State.
The Active Set pilot shall be the pilot associated with the Control Channel the access terminal
12is currently monitoring. The access terminal shall return an IdleHO indication when the Active
13Set changes in the Idle State.
10
11
73
3GPP2 C.P0087-0 v0.83
The access terminal shall not change its Active Set pilot at a time that causes it to miss a
2synchronous Control Channel capsule. Other rules governing when to replace this Active Set
3pilot are beyond the scope of this specification.
1
If the access terminal receives a TrafficChannelAssignment message, it shall set its Active Set
5to the list of pilots specified in the message if the TrafficChannelAssignment message does not
6contain a Channel Record, or if the TrafficChannelAssignment message contains a Channel
7Record and the access terminal supports the CDMA Channel specified by the Channel Record.
4
5.4.6.1.5.2 Pilot Channel Supervision in the Idle State
The access terminal shall perform pilot channel supervision in the Idle State as follows:
10
11
12
13
14
15
16
17
18
19
Access terminal shall monitor the pilot strength of the pilot in its active set, all the pilots in
the candidate set and all the pilots in the neighbor set that are on the same frequency.
If the strength of all the pilots that the access terminal is monitoring goes below the value
specified by PilotDrop, the access terminal shall start a pilot supervision timer. The access
terminal shall consider the timer to be expired after the time specified by PilotDropTimer.
If the strength of at least one of the pilots goes above the value specified by PilotDrop while
the pilot supervision timer is counting down, the access terminal shall reset and disable
the timer.
If the pilot supervision timer expires, the access terminal shall return a NetworkLost
indication.
5.4.6.1.5.3 Processing the TrafficChannelAssignment Message in the Idle State
20
If the access terminal receives a TrafficChannelAssignment message in this state, it shall

perform the following if the TrafficChannelAssignment message does not contain a Channel
23Record, or if the TrafficChannelAssignment message contains a Channel Record and the
24access terminal supports the CDMA Channel specified by the Channel Record:
21
22
25
Update its Active Set as described in 5.4.6.1.5.1
27
Set the following public data of the Forward Traffic Channel MAC Protocol to the
corresponding fields of the TrafficChannelAssignment message:
28
DRCLength
29
ACKChannelGain
30
DRCCover for every pilot in the Active Set
31
DSC for every cell in the Active Set
26
32
33
34
35
36
If the Forward Traffic Channel MAC protocol defines the DRCChannelGainBase as a public
data, then set that public data to the DRCChannelGainBase field of the
TrafficChannelAssignment message. Otherwise, set the DRCChannelGain public data of
the Forward Traffic Channel MAC protocol to the DRCChannelGainBase field of the
TrafficChannelAssignment message.
74
3GPP2 C.P0087-0 v0.83
1
2
3
If the Forward Traffic Channel MAC protocol defines the DSCChannelGainBase as a public
data, then set that public data to the DSCChannelGainBase field of the
Set the following public data of the Reverse Traffic Channel MAC Protocol to the
corresponding fields of the TrafficChannelAssignment message:
RAChannelGain for every pilot in the Active Set
RABLength for every pilot in the Active Set
RABOffset for every pilot in the Active Set
14
If MACIndexMSB fields are included in the TrafficChannelAssignment message, then the

access terminal shall determine the 7-bit MACIndex for each pilot in the Active Set by
prepending the corresponding MACIndexMSB field of the TrafficChannelAssignment
message to the corresponding MACIndexLSBs field of the TrafficChannelAssignment
message. Otherwise the access terminal shall set the MACIndex to the corresponding
MACIndexLSBs field.
15
Return a ConnectionInitiated Indication.
9
10
11
12
13
17
If the Channel Record is included in the message, then the access terminal shall tune to
the CDMA Channel specified by the Channel Record.
18
Issue the following commands:
19
ReverseTrafficChannelMAC.Activate
20
ForwardTrafficChannelMAC.Activate
21
AccessChannelMAC.Deactivate
22
Transition to the Connected State.
16
23
5.4.6.1.5.4 Route Update Report Rules
24
The access terminal shall send RouteUpdate messages to update its location with the access
26network.
25
The access terminal shall not send a RouteUpdate message if the state timer of the Connection
Setup State in the Idle State Protocol is active.
27
28
The access terminal shall comply with the following rules regarding RouteUpdate messages:
29
30
31
32
33
34
35
36
The Inter-RAT Route Update Protocol shall send a RouteUpdate message upon receiving a
SendRouteUpdate command.
If the value of the SupportRouteUpdateEnhancements attribute is not 0x00, then the
access terminal shall send a RouteUpdate message whenever it receives a
RouteUpdateRequest message.
The access terminal shall send a RouteUpdate message with every access channel capsule
transmitted by the access terminal.
75
3GPP2 C.P0087-0 v0.83
1
2
The access terminal shall include in the RouteUpdate message the pilot PN phase, pilot
strength, and drop timer status for every pilot in the Active Set and Candidate Set.
The access terminal shall send a RouteUpdate message if all of the following conditions are
true:
the RouteUpdateRadiusOverhead field of the SectorParameters message is not set to

zero, and
the value of the RouteUpdateRadiusMultiply attribute is not 0x00, and
the computed value r is greater than max ( 0, rm ro + ra ), where ro is the value

provided in the RouteUpdateRadiusOverhead field of the SectorParameters message
transmitted by the sector in which the access terminal last sent a RouteUpdate
message, rm is the value of the RouteUpdateRadiusMultiply attribute, and ra is the
value of the RouteUpdateRadiusAdd attribute.
9
10
11
12
13
14
The access terminal shall set the ReferencePilotChannelIncluded field of the RouteUpdate
message to 0,.
If (xL,yL) are the longitude and latitude of the sector to which the access terminal last sent a
16RouteUpdate, and (xC,yC) are the longitude and latitude of the sector currently providing
41
17coverage to the access terminal, then r is given by
15
yL

xC x L cos 180 14400
16
18
2
yC y L
The access terminal shall compute r with an error of no more than 5% of its true value when
|yL/14400| is less than 60 and with an error of no more than 7% of its true value when |
42
21yL/14400| is between 60 and 70 .
19
20
If the value of the SupportRouteUpdateEnhancements attribute is 0x00, then the access

network shall not send a RouteUpdateRequest message. If the value of the
24SupportRouteUpdateEnhancements attribute is not 0x00, then the access network may send a
25RouteUpdateRequest message.
22
23
5.4.6.1.6 Connected State
26
In this state, RouteUpdate messages from the access terminal are based on changes in the
radio link between the access terminal and the access network, obtained through pilot
29strength measurements at the access terminal.
27
28
The
access
network
determines
TrafficChannelAssignment messages.
30
the
contents
of
the
Active
Set
31
41 The xs denote longitude and the ys denote latitude.
L
L
L
L
76
through
3GPP2 C.P0087-0 v0.83
In the Connected State, the access terminal shall perform the following:
If the protocol receives a ReverseTrafficChannelMAC.LinkAcquired indication the access

terminal shall:
Send a TrafficChannelComplete message with the MessageSequence field of the

message set to the MessageSequence field of the TrafficChannelAssignment message,
Return a ConnectionOpened indication.
6
7
In the Connected State, the access network shall perform the following:
10
11
If the protocol receives a ReverseTrafficChannelMAC.LinkAcquired indication the access

network shall return a ConnectionOpened indication.
5.4.6.1.6.3 Active Set Maintenance
12
5.4.6.1.6.3.1 Access Network
13
Whenever the access network sends a TrafficChannelAssignment message to the access

15terminal, it shall add to the Active Set any pilots listed in the message that are not currently in
16the Active Set. Upon sending a TrafficChannelAssignment message, the access network shall
17set the following public data of the Forward Traffic Channel MAC Protocol to the corresponding
18fields of the TrafficChannelAssignment message:
14
19
DRCLength
20
ACKChannelGain
21
22
23
24
25
26
27
28
29
30
Upon sending a TrafficChannelAssignment message, the access network shall set the following
32public data of the Reverse Traffic Channel MAC Protocol to the corresponding fields of the
33TrafficChannelAssignment message:
31
34
35
36
77
3GPP2 C.P0087-0 v0.83
The access network shall delete a pilot from the Active Set if the pilot was not listed in a
message
and
if
the
access
network
received
the
3TrafficChannelComplete message, acknowledging that TrafficChannelAssignment message.
1
The access network should send a TrafficChannelAssignment message to the access terminal
5in response to changing radio link conditions, as reported in the access terminals
6RouteUpdate messages.
4
The access network should only specify a pilot in the TrafficChannelAssignment message if it
8has allocated the required resources in the associated sector. This means that the sector
9specified by the pilot is ready to receive data from the access terminal and is ready to transmit
10queued data to the access terminal should the access terminal point its DRC at that sector.
7
If the SupportedCDMAChannels attribute contains one or more band classes, then the access
network shall assign a Traffic Channel on a CDMA Channel supported by the access terminal
13as indicated by the value of the SupportedCDMAChannels attribute.
11
12
If the access network adds or deletes a pilot in the Active Set, it shall send an ActiveSetUpdated
indication.
14
15
If the access network adds a pilot specified in a RouteUpdate message to the Active Set, the
17access network may use the PilotPNPhase field provided in the message to obtain a round trip
18delay estimate from the access terminal to the sector associated with this pilot. The access
19network may use this estimate to accelerate the acquisition of the access terminals Reverse
20Traffic Channel in that sector.
16
5.4.6.1.6.3.2 Access Terminal
21
If the access terminal receives a valid TrafficChannelAssignment message (see 5.4.6.1.3.2), it

shall replace the contents of its current Active Set with the pilots specified in the message. The
24access terminal shall process the message as defined in 5.4.6.1.6.6.
22
23
5.4.6.1.6.4 ResetReport Message
25
The access network may send a ResetReport message to reset the conditions under which
27RouteUpdate messages are sent from the access terminal. Access terminal usage of the
28ResetReport message is specified in the following section.
26
5.4.6.1.6.5 Route Update Report Rules
29
The access terminal sends a RouteUpdate message to the access network in this state to
request addition or deletion of pilots from its Active Set. If the access terminal is sending the
32RouteUpdate message in response to a RouteUpdateRequest message that contains a Channel
33record, the access terminal shall include in a RouteUpdate message the pilot PN phase, pilot
34strength, and drop status for pilots whose strength is above the value specified by PilotAdd and
35subject to the following conditions:
30
31
36
37
38
39
If the RouteUpdateRequest message contains one or more SectorPilotPN fields, the access
terminal shall include pilots in the CDMA channel indicated by the Channel record and
that are indicated by the SectorPilotPN fields. Otherwise, the access terminal shall include
pilots which are in the CDMA channel indicated by the Channel record.
78
3GPP2 C.P0087-0 v0.83
If the access terminal is not sending the RouteUpdate message in response to a

2RouteUpdateRequest message that contains a Channel record, the access terminal shall
3determine which pilots to include in the RouteUpdate message as follows:
1
4
5
6
7
8
9
10
If DynamicThresholds is equal to 0, the access terminal shall include in the RouteUpdate

message the pilot PN phase, pilot strength, and drop timer status for every pilot in the
Active Set and Candidate Set. If DynamicThresholds is equal to 1, then the access
terminal shall include in the RouteUpdate message the pilot PN phase, pilot strength, and
drop timer status for every pilot in the Active Set, for each pilot in the Candidate Set whose
strength is above the values specified by PilotAdd, and for each pilot in the Candidate set
whose strength, PS, satisfies the following inequality:
10 log 10 PS
11
SoftSlope
AddInterce pt
10 log 10 PS i
,
8
2
iA
where the summation is performed over all pilots currently in the Active Set.
12
The access terminal shall send a RouteUpdate message if any one of the following occurs:
13
15
The value of the SupportRouteUpdateEnhancements attribute is not 0x00 and the access
terminal receives a RouteUpdateRequest message.
16
The Inter-RAT Route Update Protocol receives a SendRouteUpdate command.
14
17
18
19
20
If DynamicThresholds is equal to 0 and the strength of a Neighbor Set or Remaining Set

pilot is greater than the value specified by PilotAdd.
If DynamicThresholds is equal to 1 and the strength of a Neighbor Set or Remaining Set
pilot, PS, satisfies the following inequality:
AddInterce pt PilotAdd
SoftSlope
10 log10 PSi
,
8
2
2
iA
21
10 log10 PS > max
22
where the summation is performed over all pilots currently in the Active Set.
23
24
25
26
If DynamicThresholds is equal to 0 and the strength of a Candidate Set pilot is greater

than the value specified by PilotCompare above an Active Set pilot, and a RouteUpdate
message carrying this information has not been sent since the last ResetReport message
was received.
29
If DynamicThresholds is equal to 0 and the strength of a Candidate Set pilot is above

PilotAdd, and a RouteUpdate message carrying this information has not been sent since
the last ResetReport message was received.
30
If DynamicThresholds is equal to 1 and
31
27
28
10 log 10 PS
32
35
SoftSlope
AddInterce pt
10 log 10 PS i
8
2
iA
where the summation is performed over all pilots currently in the Active Set, and
33
34
the strength of a Candidate Set pilot, PS, satisfies the following inequality:
a RouteUpdate message carrying this information has not been sent since the last
ResetReport message was received.
79
3GPP2 C.P0087-0 v0.83
If DynamicThresholds is equal to 1 and
the strength of a Candidate Set pilot is greater than the value specified by PilotCompare
above an Active Set pilot, and
the strength of a Candidate Set pilot, PS, satisfies the following inequality:
3
4
10 log10 PS
where the summation is performed over all pilots currently in the Active Set, and
6
7
8
9
10
SoftSlope
AddInterce pt
10 log10 PSi
8
2
iA
a RouteUpdate message carrying this information has not been sent since the last
ResetReport message was received.
The pilot drop timer of an Active Set pilot has expired, and a RouteUpdate message carrying
this information has not been sent since the last ResetReport message was received.
The access terminal shall set the ReferencePilotChannelIncluded field of the RouteUpdate
message to 0,
11
12

14network
shall not send a RouteUpdateRequest message. If the value of the
15SupportRouteUpdateEnhancements attribute is not 0x00, then the access network may send a
16RouteUpdateRequest message.
13
5.4.6.1.6.6 Processing the TrafficChannelAssignment Message in the Connected State
17
If valid TrafficChannelAssignment (see 5.4.6.1.3.2) message does not contain a Channel

19Record, or if a valid TrafficChannelAssignment message contains a Channel Record and the
20access terminal supports the CDMA Channel specified by the Channel Record, then the access
21terminal shall process the message as follows:
18
23
The access terminal shall set the following public data of the Forward Traffic Channel MAC
Protocol to the corresponding fields of the TrafficChannelAssignment message:
24
DRCLength
25
ACKChannelGain
26
27
22
28
29
30
31
32
33
34
35
36
37
The access terminal shall set the following public data of the Reverse Traffic Channel MAC
Protocol to the corresponding fields of the TrafficChannelAssignment message:
80
3GPP2 C.P0087-0 v0.83
If the TrafficChannelAssignment message contains a value for the FrameOffset that is

different from the value of the FrameOffset received in the last TrafficChannelAssignment
message that was received in the Idle state, then the access terminal shall return a
RouteUpdate.AssignmentRejected indication and shall discard the message.
The access terminal shall update its Active Set as defined in 5.4.6.1.6.3.2.
4
5
6
9
10
11
12
13
14
15
16
17
18
19
20
21
22
The access terminal shall tune to the CDMA Channel defined by the Channel Record, if
this record is included in the message.
If MACIndexMSB fields are included in the TrafficChannelAssignment message, then the
access terminal shall determine the 7-bit MACIndex for each pilot in the Active Set by
prepending the corresponding MACIndexMSB field of the TrafficChannelAssignment
message to the corresponding MACIndexLSBs field of the TrafficChannelAssignment
message. Otherwise the access terminal shall set the MACIndex to the corresponding
MACIndexLSBs field.
The access terminal shall start monitoring and responding to the Power Control Channels
defined by the MACIndex fields provided in the message. The access terminal should use
the SofterHandoff fields to identify the Power Control Channels that are carrying identical
information and can therefore be soft-combined.
The access terminal shall send the access network a TrafficChannelComplete message
specifying the MessageSequence value received in the TrafficChannelAssignment message.
5.4.6.1.6.7 Processing the TrafficChannelComplete Message
23
The access network should set a transaction timer when it sends a TrafficChannelAssignment
25message. If the access network sets a transaction timer, it shall reset the timer when it receives
26a TrafficChannelComplete message containing a MessageSequence field equal to the one sent
27in the TrafficChannelAssignment message.
24
If the timer expires, the access network should return a ConnectionLost indication.
28
5.4.6.1.6.8 Transmission and Processing of the NeighborList Message
29
The access network may send the NeighborList message to the access terminal when the
31protocol is in the Connected State to override the search window size and/or search window
32offset corresponding to a pilot in the Neighbor Set.
30
Upon receiving a NeighborList message, the access terminal shall perform the following in the
34order specified:
33
35
36
The access terminal shall remove all Neighbor structures from

NeighborListMessageNeighborList.
81
3GPP2 C.P0087-0 v0.83
For each pilot (specified by its pilot PN and its channel) listed in the received NeighborList
message, the access terminal shall add a Neighbor structure to
NeighborListMessageNeighborList and populate it as follows:
Set the structures PilotPN field to the messages corresponding PilotPN field.
If the messages ChannelIncluded field is set to 1, set the structures Channel field to
the messages corresponding Channel field. Otherwise, set the structures Channel field
to the current channel.
If the messages SearchWindowSizeIncluded field is set to 1, then set the structures

SearchWindowSize field to the messages corresponding SearchWindowSize field.
Otherwise, set the structures SearchWindowSize field to NULL.
If the SearchWindowOffsetIncluded field is set to 1, then set the structures

SearchWindowOffset field to the messages corresponding SearchWindowOffset field.
Otherwise, set the structures SearchWindowOffset field to NULL.
1
2
6
7
8
9
10
11
12
13
14
Perform the procedures specified in 5.4.6.1.2.1.
15
The access network may send the AttributeOverride message to the access terminal to override
the
parameters
specified
in
the
SetManagementSameChannelParameters
and
18SetManagementDifferentChannelParameters configuration attributes.
16
17
If the value of the SetManagementOverrideAllowed attribute is 0x01, then upon receiving a

valid (see 5.4.6.1.3.3) AttributeOverride message, the access terminal shall start using the
21values specified in the message.
19
20
The access terminal shall discard the values of the SetManagementSameChannelParameters

and SetManagementDifferentChannelParameters in the AttributeOverride message if the
24SetManagementOverrideAllowed attribute is set to 0x00.
22
23
When the access terminal receives a valid (see 5.4.6.1.3.3) AttributeOverride message, it shall
send the access network an AttributeOverrideResponse message specifying the
27MessageSequence value received in the AttributeOverride message.
25
26
5.4.6.1.6.10 Processing of OverheadMessages.Updated Indication
28
Upon receiving OverheadMessages.Updated indication, the access terminal shall perform the
30OverheadMessagesNeighborList Initialization procedures as specified in 5.4.6.1.6.11 and then
31perform the procedures specified in 5.4.6.1.2.1.
29
5.4.6.1.6.11 OverheadMessagesNeighborList Initialization
32
When the OverheadMessagesNeighborList initialization procedures are invoked by the access

terminal, it shall perform the following:
33
34
35
36
The access terminal shall remove all Neighbor structures from the
OverheadMessagesNeighborList list.
82
3GPP2 C.P0087-0 v0.83
For each pilot (specified by its pilot PN and its channel) in the neighbor list given as public
data of Overhead Messages Protocol, the access terminal shall add a Neighbor structure to
the OverheadMessagesNeighborList list and populate it as follows:
Set the structures PilotPN field to the corresponding NeighborPilotPN field given as
public data of the Overhead Messages Protocol.
If the Overhead Messages Protocols NeighborChannelIncluded field is set to 1, set the

structures Channel field to the Overhead Messages Protocols corresponding
NeighborChannel. Otherwise, set the structures Channel field to the current channel.
If the Overhead Messages Protocols SearchWindowSizeIncluded field is set to 1, then

set the structures SearchWindowSize field to the Overhead Messages Protocols
corresponding
SearchWindowSize
field.
Otherwise,
set
the
structures
SearchWindowSize field to NULL.
If the Overhead Messages Protocols SearchWindowOffsetIncluded field is set to 1, then

set the structures SearchWindowOffset field to the Overhead Messages Protocols
corresponding
SearchWindowOffset
field.
Otherwise,
set
the
structures
SearchWindowOffset field to NULL.
1
2
5
6
7
8
9
10
11
12
13
14
15
16
5.4.6.1.7 Tunnel State (editor: move this section after the Connected State section)
17
18
19
20
21
22
23
24
25
Remove all Neighbor structures from NeighborListMessageNeighborList and perform the

procedures specified in 5.4.6.1.2.1.
Stop using the parameters specified in the AttributeOverride message in the set
management procedures and start using values specified by the
SetManagementSameChannelParameters and the
SetManagementDifferentChannelParameters attributes whichever applicable, in the set
management procedures.
If the protocol receives a SignalingAdaptation.IdleHandoff indication, the access terminal shall:
26
27
28
If the access terminal receives a SignalingAdaptation.ConnectionInitiated indication in this

state, then the access terminal shall return a ConnectionInitiated indication.
29
30
5.4.6.1.7.1 Pilot Sets Maintenance
31
In the Tunnel State, the access terminal shall perform the Active Set maintenance following the
same procedures specified in section 5.4.6.1.5.1 with the only exception:
32
33
The access terminal shall not return an IdleHO indication when the Active Set changes in the
35Tunnel State.
34
In the Tunnel State, the access terminal shall maintain the Candidate Set and Neighbor Set,
and may maintain the Remaining Set following the same procedures specified in sections
385.4.6.1.2.6, 5.4.6.1.2.7 and 5.4.6.1.2.8 respectively.
36
37
83
3GPP2 C.P0087-0 v0.83
5.4.6.1.7.1.1 Active Set Maintenance
The access network shall not initially maintain an Active Set for the access terminal in this
3state.
2
The access terminal shall initially keep an Active Set of size one when it is in the Tunnel State.
If the access terminal is currently monitoring the Control Channel:
5
6
The Active Set pilot shall be the pilot associated with the Control Channel the access
terminal is currently monitoring. The access terminal shall return an IdleHO
indication when the Active Set changes in the Idle State.
The access terminal shall not change its Active Set pilot at a time that causes it to miss
a synchronous Control Channel capsule. Other rules governing when to replace this
Active Set pilot are beyond the scope of this specification.
7
8
9
10
11
12
13
Otherwise:
The Active Set pilot shall be the pilot the access terminal uses as reference pilot.
If the access terminal receives a TrafficChannelAssignment message, it shall set its Active Set
to the list of pilots specified in the message if the TrafficChannelAssignment message does not
16contain a Channel Record, or if the TrafficChannelAssignment message contains a Channel
17Record and the access terminal supports the CDMA Channel specified by the Channel Record.
14
15
5.4.6.1.7.2 Pilot Channel Supervision in the Tunnel State
18
The access terminal shall perform pilot channel supervision in the Tunnel State following the
procedures specified in section 5.4.6.1.5.2
19
20
5.4.6.1.7.3 Processing the TrafficChannelAssignment Message in the Tunnel State
21
If the access terminal receives a TrafficChannelAssignment message in this state, it shall

process the TrafficChannelAsssignment message following the procedures specified in section
245.4.6.1.5.3.
22
23
5.4.6.1.7.4 Route Update Report Rules in the Tunnel State
25
The access terminal shall comply with the following rules regarding RouteUpdate messages:
26
27
28
29
30
31
32
33
34
35
36
37
The Inter-RAT Route Update Protocol shall send a RouteUpdate message together with the
ConnectionRequest message when the active handoff from the other radio access
technology to HRPD occurs.
The Inter-RAT Route Update Protocol shall send a RouteUpdate message upon receiving a
SendRouteUpdate command.
If the value of the SupportRouteUpdateEnhancements attribute is not 0x00, then the
access terminal shall send a RouteUpdate message whenever it receives a
RouteUpdateRequest message.
The access terminal shall set the ReferencePilotChannelIncluded field, and the
ReferencePilotChannel field to the channel record (see [1]) of the reference pilot if this field
is included in the message.
84
3GPP2 C.P0087-0 v0.83
1
2
The access terminal shall include the pilot PN phase, pilot strength, and drop timer status
for every pilot in the Active Set and Candidate Set in the RouteUpdate message.
The access terminal shall send a RouteUpdate43 message if all of the following conditions
4
are true:
3
the RouteUpdateRadiusOverhead field of the SectorParameters message is not set to

zero, and
the value of the RouteUpdateRadiusMultiply attribute is not 0x00, and
the computed value r is greater than max (0, rm ro + ra ), where ro is the value
provided in the RouteUpdateRadiusOverhead field of the SectorParameters message
transmitted by the sector in which the access terminal used as ReferencePilotChannel
when it last sent a RouteUpdate message, rm is the value of the
RouteUpdateRadiusMultiply
attribute,
and
ra
is
the
value
of
the
RouteUpdateRadiusAdd attribute.
5
6
9
10
11
12
13
If (xL,yL) are the longitude and latitude of the sector to which the access terminal last sent a
15RouteUpdate, and (xC,yC) are the longitude and latitude of the sector currently providing
44
16coverage to the access terminal, then r is given by
14
yL

xC x L cos 180 14400
16
17
2
yC y L
18
19
20
The access terminal shall compute r with an error of no more than 5% of its true value
when |yL/14400| is less than 60 and with an error of no more than 7% of its true value
when |yL/14400| is between 60 and 7045.
21
5.4.6.2.1 RouteUpdate
22
The access terminal sends the RouteUpdate message to notify the access network of its current
location and provide it with an estimate of its surrounding radio link conditions.
23
24
25
43 This applies when the access terminal is currently monitoring the Control Channel.
44 The xs denote longitude and the ys denote latitude.
L
L
L
L
85
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
MessageSequence
ReferencePilotPN
ReferencePilotStrength
ReferenceKeep
NumPilots
NumPilots occurrences of the following fields:

PilotPNPhase
15
ChannelIncluded
Channel
0 or 24
PilotStrength
Keep
CompatibleReserved
ReferencePilotChannelIncluded
ReferencePilotChannel
0 or 24
Reserved
Variable
MessageID
MessageSequence
The access terminal shall set this field to the sequence number of this
message. The sequence number of this message is 1 more than the
sequence number of the last RouteUpdate message (modulo 2 8) sent by
this access terminal. If this is the first RouteUpdate message sent by the
access terminal, it shall set this field to 0x00.
2
3
4
5
6
ReferencePilotPN
7
8
9
The access terminal shall set this field to the access terminals time
reference (the reference pilot), relative to the zero offset pilot PN sequence
in units of 64 PN chips.
ReferencePilotStrength
11
The access terminal shall set this field to 2 10 log 10 PS , where PS
10
12
13
14
15
is the strength of the reference pilot, measured as specified in

5.4.6.1.2.3. If this value is less than 0, the access terminal shall set this
field to 000000. If this value is greater than 111111, the access
terminal shall set this field to 111111.
86
3GPP2 C.P0087-0 v0.83
ReferenceKeep
1
2
3
NumPilots
4
5
PilotPNPhase
6
7
ChannelIncluded
8
9
10
Channel
11
12
13
14
PilotStrength
15
16
17
18
19
Keep
20
21
22
If the pilot drop timer corresponding to the reference pilot has expired,
the access terminal shall set this field to 0; otherwise, the access
The access terminal shall set this field to the number of pilots that follow
this field in the message.
The PN offset in resolution of 1 chip of a pilot in the Active Set or
Candidate Set of the access terminal that is not the reference pilot.
The access terminal shall set this field to 1 if the channel for this pilot
offset is not the same as the current channel. Otherwise, the access
The access terminal shall include this field if the ChannelIncluded field
is set to 1. The access terminal shall set this to the channel record
corresponding to this pilot (see section 14.1 of [1]). Otherwise, the
access terminal shall omit this field for this pilot offset.
The access terminal shall set this field to 2 10 log 10 PS , where PS
is the strength of the pilot in the above field, measured as specified in
5.4.6.1.2.3. If this value is less than 0, the access terminal shall set this
field to 000000. If this value is greater than 111111, the access
If the pilot drop timer corresponding to the pilot in the above field has
expired, the access terminal shall set this field to 0; otherwise, the
access terminal shall set this field to 1.
CompatibleReserved The access terminal shall always set this bit to 0.
23
ReferencePilotChannelIncluded
24
25
26
27
The access terminal shall set this field to 1 if the channel for the
reference pilot is included in this message, otherwise, the access
ReferencePilotChannel
28
29
30
31
32
Reserved
33
34
35
If the ReferencePilotChannelIncluded field is set to 1, the access

terminal shall set this field to the channel record (see [1]) corresponding
to the reference pilot. Otherwise, the access terminal shall omit this
field.
The number of bits in this field is equal to the number needed to make
the message length an integer number of octets. This field shall be set to
all zeros.
87
3GPP2 C.P0087-0 v0.83
Channels
AC
Addressing
RTC
unicast
SLP
Reliable 46
Priority
Best Effort
20
5.4.6.2.2 TrafficChannelAssignment
The access network sends the TrafficChannelAssignment message to manage the access
terminals Active Set.
3
4
5
88
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
MessageSequence
ChannelIncluded
Channel
0 or 24
FrameOffset
DRCLength
DRCChannelGainBase
ACKChannelGain
NumPilots
NumPilots occurrences of the following record:

PilotPN
SofterHandoff
MACIndexLSBs
DRCCover
RABLength
RABOffset
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
89
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
Reserved
Variable
MessageID
MessageSequence
field of the last TrafficChannelAssignment message (modulo 2 S, S=8)
sent to this access terminal.
2
3
4
ChannelIncluded
5
6
7
Channel
8
9
10
11
12
13
FrameOffset
14
15
16
DRCLength
17
18
19
The access network shall set this field to 1 if the Channel record is
included for these pilots. Otherwise, the access network shall set this
field to 0.
The access network shall include this field if the ChannelIncluded field
is set to 1. The access network shall set this to the channel record
corresponding to this pilot (see section 14.1 of [1]). Otherwise, the
access network shall omit this field for this pilot offset. If Channel is
included, the access network shall set the SystemType field of the
Channel record to 0000.
The access network shall set this field to the frame offset the access
terminal shall use when transmitting the Reverse Traffic Channel, in
units of slots.
The access network shall set this field to the number of slots the access
terminal shall use to transmit a single DRC value, as shown in Table
5.4.6.2 -13.
Table 5.4.6.2-13. DRCLength Encoding
20
Field
value
(binary)
DRCLength
(slots)
00
01
10
11
DRCChannelGainBase
21
22
23
24
25
The access network shall set this field to the ratio of the power level of
the DRC Channel (when it is transmitted) to the power level of the
Reverse Traffic Pilot Channel expressed as 2's complement value in units
of 0.5 dB. The valid range for this field is from 9 dB to +6 dB, inclusive.
90
3GPP2 C.P0087-0 v0.83
1
2
ACKChannelGain
3
4
5
6
7
NumPilots
8
9
PilotPN
10
11
12
13
14
SofterHandoff
15
16
17
18
19
20
21
MACIndexLSBs
22
23
24
DRCCover
25
26
RABLength
27
28
29
30
31
32
The access terminal shall support all the values in the valid range for
this field.
The access network shall set this field to the ratio of the power level of
the Ack Channel (when it is transmitted) to the power level of the Reverse
Traffic Pilot Channel expressed as 2's complement value in units of 0.5
dB. The valid range for this field is from 3 dB to +6 dB, inclusive. The
access terminal shall support all the values in valid range for this field.
The access network shall set this field to the number of pilots included
in this message.
The access network shall set this field to the PN Offset associated with
the sector that will transmit a Power Control Channel to the access
terminal, to whom the access terminal is allowed to point its DRC, and
whose Control Channel and Forward Traffic Channel the access terminal
may monitor.
If the Forward Traffic Channel associated with this pilot will carry the
same closed-loop power-control bits as that of the previous pilot in this
message, the access network shall set this field to 1; otherwise, the
access network shall set this field to 0. The access network shall set the
first instance of this field to 0. If the SofterHandoff field associated with
a PilotPN is equal to 1, then the PilotPN is defined to belong to the same
cell as the previous PilotPN in this message.
Least Significant Bits of the Medium Access Control Index. The access
network shall set this field to the six least significant bits of the
MACIndex assigned to the access terminal by this sector.
The access network shall set this field to the index of the DRC cover
associated with the sector specified in this record.
If the traffic channel being assigned by this
or Subtype 1 Reverse Traffic Channel MAC
shall set the RABLength to specify the
according to Table 5.4.6.2.2-2. Otherwise,
this field to 00.
Table 5.4.6.2-14. Encoding of the RABLength Field

Field value (binary)
message is to use Subtype 0

protocol, the access network
Reverse Activity Bit length
the access network shall set
RABLength (slots)
00
01
16
10
32
11
64
91
3GPP2 C.P0087-0 v0.83
RABOffset
2
3
4
5
6
7
If the traffic channel being assigned by this message is to use Subtype 0

or Subtype 1 Reverse Traffic Channel MAC protocol, the access network
shall set this field to indicate the offset associated with the Reverse
Activity Bit. Otherwise, the access network shall set this field to 000.
The value (in slots) of RABOffset is the number the field is set to
multiplied by RABLength/8.
RAChannelGainIncluded
If this field is included, the access network shall set this field as follows:
10
If RAChannelGain field is included in this message, then the access
11
network shall set this field to 1. Otherwise, the access network shall set
12
this field to 0.
8
9
RAChannelGain
13
14
15
16
17
18
19
20
21
22
If RAChannelGainIncluded field is not included in this message or if

RAChannelGainIncluded field is equal to 0, then the access network
shall omit this field. Otherwise, the access network shall set this field as
follows:
The ith occurrence of this field corresponds to the ith occurrence of the
PilotPN field in this message. The access network shall set the ith
occurrence of this field to the RA Channel Gain to be used by the access
terminal according to Table 5.4.6.2 -15 of the ith PilotPN. The access
terminal uses this information to demodulate the RA Channel.
Table 5.4.6.2-15. Reverse Activity Channel Gain Encoding
Field
value
(binary)
RA Channel Gain
(dB)
00
01
10
12
11
15
MACIndexMSBsIncluded
If the RAChannelGainIncluded field is not included in this message or if
25
RAChannelGainIncluded field is equal to 0, then the access network
26
27
follows: If MACIndexMSB fields are included in this message, then the
28
access network shall set this field to 1. Otherwise, the access network
29
shall set this field to 0.
23
24
MACIndexMSB
30
31
32
Most significant bit of the Medium Access Control Index. If

MACIndexMSBsIncluded field is not included in this message or if
MACIndexMSBsIncluded field is equal to 0, then the access network
92
3GPP2 C.P0087-0 v0.83
follows:
1
2
The ith occurrence of this field corresponds to the ith occurrence of the
PilotPN field in this message. The access network shall set the ith
occurrence of this field to the most significant bit of the 7-bit MACIndex
assigned to the access terminal by the ith PilotPN.
3
4
5
6
DSCChannelGainBase
If MACIndexMSBsIncluded field is not included in this message or if

shall omit this field. Otherwise, the access network shall set this field to
the power of the DSC channel relative to the pilot channel in units of
0.5 dB, in the range from zero to 15.5 dB, inclusive.
8
9
10
11
12
DSC
If MACIndexMSBsIncluded field is not included in this message or if

follows: The access network shall set the ith occurrence of this field to
the DSC associated with the ith cell specified by the PilotPN fields in this
message.
13
14
15
16
17
18
Reserved
the message length an integer number of octets. This field shall be set to
all zeros.
19
20
21
22
Channels
CC
SLP
FTC
Addressing
unicast
Reliable
Priority
Best Effort47
20
5.4.6.2.3 TrafficChannelComplete
23
The access terminal sends the TrafficChannelComplete message to provide an acknowledgment

25for the TrafficChannelAssignment message.
24
26
Field
MessageID
27
Length (bits)
MessageID
MessageSequence
47 The TrafficChannelAssignment message sent in response to the Open command is sent using best
3effort
SLP. All subsequent TrafficChannelAssignment messages are sent using reliable delivery SLP.
93
3GPP2 C.P0087-0 v0.83
MessageSequence
1
2
3
4
the TrafficChannelAssignment message whose receipt this message is
acknowledging.
Channels
RTC
Addressing
unicast
SLP
Reliable
Priority
40
5.4.6.2.4 ResetReport
The access network sends the ResetReport message to reset the RouteUpdate transmission
7rules at the access terminal.
6
Field
Length (bits)
MessageID
MessageID
10
Channels
Addressing
SLP
FTC
unicast
Priority
Reliable
40
5.4.6.2.5 NeighborList
11
The NeighborList message is used to convey information corresponding to the neighboring

13sectors to the access terminals when the access terminal is in the Connected State.
12
14
94
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
Count
Count occurrences of the following field:

PilotPN
Count occurrences of the following two fields:

ChannelIncluded
Channel
0 or 24
SearchWindowSizeIncluded
Count occurrences of the following field

SearchWindowSize
0 or 4
SearchWindowOffsetIncluded
Count occurrences of the following field

SearchWindowOffset
0 or 3
FPDCHSupportedIncluded
0 or 1
m, 0 m Count. occurrences of the following field:

FPDCHSupported
0 or 1
Reserved
Variable
MessageID
Count
The access network shall set this field to the number of records
specifying neighboring sectors information included in this message.
2
3
PilotPN
4
5
6
ChannelIncluded
7
8
9
The access network shall set this field to the PN Offset of a neighboring
sector for which the access network is providing search window
information in this message.
The access network shall set this field to 1 if a Channel record is
included for this neighbor, and to 0 otherwise. The access network shall
omit this field if the corresponding NeighborChannelIncluded field is set
95
3GPP2 C.P0087-0 v0.83
1
2
3
Channel
4
5
6
7
to 0. Otherwise, if included, the nth occurrence of this field corresponds

to the nth occurrence of PilotPN in the record that contains the PilotPN
field above.
Channel record specification for the neighbor channel. See 14.1 of [1] for
the Channel record format. The nth occurrence of this field corresponds
to the nth occurrence of PilotPN in the record that contains the PilotPN
field above.
SearchWindowSizeIncluded
The access network shall set this field to 1 if SearchWindowSize field for
10
neighboring sectors is included in this message. Otherwise, the access
11
network shall set this field to 0.
8
9
SearchWindowSize
12
13
14
15
16
17
The access network shall omit this field if SearchWindowSizeIncluded is

set to 0. If SearchWindowSizeIncluded is set to 1, the access network
shall set this field to the value shown in Table 5.4.6.2 -16 corresponding
to the search window size to be used by the access terminal for the
neighbor pilot. The nth occurrence of this field corresponds to the nth
occurrence of PilotPN in the record that contains the PilotPN field above.
96
3GPP2 C.P0087-0 v0.83
Table 5.4.6.2-16. Search Window Sizes

SearchWindowSize Value
Search Window Size

(PN chips)
10
14
20
28
40
60
80
10
100
11
130
12
160
13
226
14
320
15
452
SearchWindowOffsetIncluded
The access network shall set this field to 1 if SearchWindowOffset field
4
for neighboring sectors is included in this message. Otherwise, the
5
2
3
SearchWindowOffset
6
7
8
9
10
11
12
13
The access network shall omit this field if SearchWindowOffsetIncluded

is set to 0. If SearchWindowOffsetIncluded is set to 1, the access
network shall set this field to the value shown in Table 5.4.6.2 -17
corresponding to the search window offset to be used by the access
terminal for the neighbor pilot. The nth occurrence of this field
corresponds to the nth occurrence of PilotPN in the record that contains
the PilotPN field above.
97
3GPP2 C.P0087-0 v0.83
Table 5.4.6.2-17. Search Window Offset
SearchWindowOffset
Offset ( PN chips)
WindowSize 48 /2
WindowSize
3 WindowSize /2
- WindowSize /2
- WindowSize
-3 WindowSize /2
Reserved
4
5
6
FPDCHSupported
The access network shall set this field to 0 if the FPDCHSupported
fields are omitted. Otherwise, the access network shall set this field to
1.
12
If FPDCHSupportedIncluded is not included or is included and is set to

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

record that has SystemType equal to 0x01 supports the Forward Packet
Data Channel (see [9]), the access terminal shall set the ith occurrence
of this field to 1. Otherwise, the access network shall set the ith
occurrence of this field to 0.
the message length an integer number of octets. The access network
shall set this field to zero. The access terminal shall ignore this field.
22
48 WindowSize is pilots search window size in PN chips.
98
3GPP2 C.P0087-0 v0.83
Channels
SLP
FTC
Addressing
unicast
Reliable
Priority
40
5.4.6.2.6 AttributeOverride
The access network may send this message in order to override the configured values for the
attributes includes in this message.
2
3
4
Field
Length (bits)
MessageID
MessageSequence
One or more instances of the following record:

AttributeRecord
variable
MessageID
MessageSequence
field of the last AttributeOverride message (modulo 2 S, S=8) sent to this
access terminal.
6
7
8
The access network shall include one or more instances of the following record:
AttributeRecord
10
11
12
13
14
15
16
17
18
19
20
The access network shall set this record to the attribute record that the
access terminal is to use to override the values of the configured
attribute specified by the AttributeID of this record. See 14.3 of [1] for
the format of the attributes. The access network shall not include more
than one AttributeRecord with the same AttributeID in this message.
The access network shall include exactly one instance of attribute values
per AttributeID. The access network shall set the ValueID associated
with the complex attributes to zero. The valid attribute records that can
be
included
in
this
message
are
and
SetManagementDifferentChannelParameters.
21
Channels
Addressing
Best
Effort
SLP
FTC
unicast
Priority
40
5.4.6.2.7 AttributeOverrideResponse
22
The access terminal sends the AttributeOverrideResponse

24acknowledgment for the AttributeOverride message.
23
99
message
to
provide
an
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
MessageSequence
MessageID
The access network terminal shall set this field to 0x06.
MessageSequence
the AttributeOverride message whose receipt this message is
acknowledging.
3
4
5
6
Channels
Addressing
RTC
unicast
SLP
Priority
Best
Effort
40
5.4.6.2.8 RouteUpdateRequest
The access network sends a RouteUpdateRequest message to request the access terminal to
9send a RouteUpdate message.
8
10
100
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
ChannelIncluded
Channel
0 or 24
SectorCount
0 or 4
SectorCount occurrences of the following field:

SectorPilotPN
SectorSearchWindowSizeIncluded
0 or 1

SectorSearchWindowSize
0 or 4
SectorSearchWindowOffsetIncluded 0 or 1
SectorSearchWindowOffset
0 or 3
Reserved
0 7 (as
needed)
MessageID
ChannelIncluded
If SupportRouteUpdateEnhancements is less than 0x02 or if this

message is being sent on the Control Channel, the access network shall
set this field to 0. Otherwise, the access network may set this field to 1
to indicate that the Channel field is included or to 0 to indicate that the
Channel field is not included.
2
3
4
5
6
Channel
7
8
9
10
SectorCount
11
12
13
14
If ChannelIncluded is set to 0, the access network shall omit this field.

Otherwise, the access network shall set this field to a Channel record
specification. See 14.1 of [1] for the Channel record format. The access
network shall set the SystemType field of this record to 0x00.
Otherwise, the access network shall set this field to the number of
records specifying neighboring sectors information included in this
message.
101
3GPP2 C.P0087-0 v0.83
SectorPilotPN
1
2
3
sector for which the access terminal is to report pilot strength
information.
6
Otherwise, the access network shall set this field to 1 if
7
SectorSearchWindowSize field for neighboring sectors is included in this
8
message. Otherwise, the access network shall set this field to 0.
4
5
SectorSearchWindowSize
10
The
access
network
shall
omit
this
field
if
11
is
set
to
0.
If
12
SectorSearchWindowSizeIncluded is set to 1, the access network shall
13
set this field to the value shown in Table 5.4.6.2.8 -18 corresponding to
14
the search window size to be used by the access terminal for the
15
16
occurrence of SectorPilotPN in the record that contains the SectorPilotPN
17
field above.
9
102
3GPP2 C.P0087-0 v0.83
Table 5.4.6.2.8-18. Search Window Sizes

Search Window Size

(PN chips)
10
14
20
28
40
60
80
10
100
11
130
12
160
13
226
14
320
15
452
SectorSearchWindowOffsetIncluded
4
Otherwise, the access network shall set this field to 1 if
5
SectorSearchWindowOffset field for neighboring sectors is included in
6
this message. Otherwise, the access network shall set this field to 0.
2
3
SectorSearchWindowOffset
8
The
access
network
shall
omit
this
field
if
9
SectorSearchWindowOffsetIncluded
is
set
to
0.
If
10
SectorSearchWindowOffsetIncluded is set to 1, the access network shall
11
set this field to the value shown in Table 5.4.6.2.8 -19 corresponding to
12
the search window offset to be used by the access terminal for the
13
14
occurrence of SectorPilotPN in the record that contains the SectorPilotPN
15
field above.
7
103
3GPP2 C.P0087-0 v0.83
Table 5.4.6.2.8-19. Search Window Offset
SearchWindowOffset
Offset ( PN chips)
WindowSize 49 /2
WindowSize
3 WindowSize /2
- WindowSize /2
- WindowSize
-3 WindowSize /2
Reserved
Reserved
2
3
4
The access network shall add reserved bits to make the length of the
entire message equal to an integer number of octets. The access network
shall set this field to 0. The access terminal shall ignore this field.
Channels
FTC
Addressing
CC
unicast
SLP
Best Effort
Priority
40
The sender sends an AttributeUpdateRequest message to offer an attribute value for a given
8attribute.
7
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
The
sender
shall
increment
this
10
11
12
AttributeRecord
13
14
value
104
for
each
new
3GPP2 C.P0087-0 v0.83
Channels
FTC
Addressing
RTC
SLP
Reliable
Priority
unicast
40
The
sender
sends
an
message
in
AttributeUpdateRequest message to accept the offered attribute values.
response
to
an
3
4
Field
Length (bits)
MessageID
TransactionID
MessageID
TransactionID
6
7
8
Channels
FTC
Addressing
RTC
SLP
Reliable
Priority
unicast
40

10
in
response
to
an
11
12
Field
Length (bits)
MessageID
TransactionID
MessageID
TransactionID
13
14
15
16
Channels
Addressing
SLP
FTC
Priority
unicast
105
Reliable
40
3GPP2 C.P0087-0 v0.83
This protocol sends the following commands:
ReverseTrafficChannelMAC.Activate
ReverseTrafficChannelMAC.Deactivate
ForwardTrafficChannelMAC.Activate
ForwardTrafficChannelMAC.Deactivate
AccessChannelMAC.Activate
AccessChannelMAC.Deactivate
10
11
12
13
14
SignalingAdaptation.IdleHandoff (access terminal only)
15
Generic Attribute Update Protocol to update configurable attributes belonging to the Inter-RAT
18Route Update Protocol. If the value of the SupportRouteUpdateEnhancements attribute is not
190x00, then the access terminal and the access network shall support the use of the Generic
20Attribute Update Protocol to update values of the following attributes belonging to the Inter21RAT Route Update Protocol:
16
17
22
23
RouteUpdateRadiusAdd

25network shall not include the RouteUpdateRadiusMultiply
and RouteUpdateRadiusAdd
26attributes in an AttributeUpdateRequest message.
24
5.4.7.1 Simple Attributes
27
The configurable simple attributes for this protocol are listed in Table 5.4.7.1 -20. The access
terminal shall not include these simple attributes in a ConfigurationRequest message or an
30AttributeUpdateRequest message.
28
29
The access terminal and access network shall use as defaults the values in Table 5.4.7.1 -20
that are typed in bold italics.
31
32
106
3GPP2 C.P0087-0 v0.83
Table 5.4.7.1-20. Configurable Values
107
3GPP2 C.P0087-0 v0.83
Attribute
ID
0x03
0xff
0xfe
Attribute
SetManagementOverrideAllowed
RouteUpdateRadiusAdd
Values
Meaning
0x00
The
SetManagementSameChannelPar
ameters and
SetManagementDifferentChanne
lParameters attributes in the
AttributeOverride message are
discarded.
0x01
The
SetManagementSameChannelPar
ameters and
SetManagementDifferentChanne
lParameters attributes in the
AttributeOverride message are
acted upon.
0x020xff
Reserved
0x00
Distance-based registration is
disabled.
0x0a
Multiplier for the Route update

radius is 1.
0x01 to
0x64
Multiplier for the Route update

radius in units of 0.1.
All
other
values
Reserved
0x000
0
Addition to the Route update

radius is zero.
0x0001
to
0x0fff
Addition to the Route update

radius expressed as 2s
complement value.
All
other
values
Reserved
108
3GPP2 C.P0087-0 v0.83
Attribute
ID
0xfd
Attribute
Values
Meaning
0x00

Protocol to update
RouteUpdateRadiusMultiply and
RouteUpdateRadiusAdd and
processing of
RouteUpdateRequest message is
not supported.
0x01

Protocol to update
processing of
RouteUpdateRequest message
without Channel Record is
supported.
0x02

Protocol to update
processing of
RouteUpdateRequest message is
supported.
All
other
values
Reserved
SupportRouteUpdateEnhanceme
nts
5.4.7.2 Complex Attributes
The following complex attributes and default values are defined (see 14.3 of [1] for attribute
record definition). The following complex attributes are to be used only by the access network
4in a ConfigurationRequest message:
2
3
SearchParameters
SetManagementDifferentChannelParameters
The following complex attributes are to be used only by the access terminal in a
ConfigurationRequest message:
8
9
10
SupportedCDMAChannels
5.4.7.2.1 SearchParameters Attribute
11
12
Field
2
Length (bits)
109
Default Value
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
Default Value
AttributeID
N/A
ValueID
N/A
PilotIncrement
SearchWindowActive
SearchWindowNeighbor
10
SearchWindowRemaining
10
One or more of the following record:
Length
1
2
3
Length of the complex attribute in octets. The access network shall set
this field to the length of the complex attribute excluding the Length
field.
AttributeID
ValueID
This field identifies this particular set of values for the attribute. The
access network shall increment this field for each complex attributevalue record for a particular attribute.
5
6
7
PilotIncrement
8
9
10
11
12
13
The access network shall set this field to the pilot PN sequence
increment, in units of 64 PN chips, that access terminals are to use for
searching the Remaining Set. The access network should set this field to
the largest increment such that the pilot PN sequence offsets of all its
neighbor access networks are integer multiples of that increment. The
access terminal shall support all the valid values for this field.
SearchWindowActive
14
15
16
17
18
19
Search window size for the Active Set and Candidate Set. The access
network shall set this field to the value shown in Table 5.4.6.2 -16
corresponding to the search window size to be used by the access
terminal for the Active Set and Candidate Set. The access terminal shall
support all the valid values specified by this field.
SearchWindowNeighbor
Search window size for the Neighbor Set. The access network shall set
22
this field to the value shown in Table 5.4.6.2 -16 corresponding to the
23
search window size to be used by the access terminal for the Neighbor
24
Set. The access terminal shall support all the valid values specified by
25
this field.
20
21
SearchWindowRemaining
Search window size for the Remaining Set. The access network shall set
28
this field to the value shown in Table 5.4.6.2 -16 corresponding to the
26
27
110
3GPP2 C.P0087-0 v0.83
search window size to be used by the access terminal for the Remaining
this field.
1
2
3
5.4.7.2.2 SetManagementSameChannelParameters Attribute
The access terminal shall use these attributes if the pilot being compared is on the same
channel as the active set pilots channel.
5
6
7
Field
Length (bits)
Default Value
Length
N/A
AttributeID
N/A

{
ValueID
N/A
PilotAdd
0x0e
PilotCompare
0x05
PilotDrop
0x12
PilotDropTimer
DynamicThresholds
SoftSlope
0 or 6
N/A
AddIntercept
0 or 6
N/A
DropIntercept
0 or 6
N/A
NeighborMaxAge
Reserved
variable
N/A
}
Length
8
9
10
field.
AttributeID
ValueID
11
12
13
14
PilotAdd
15
16
This value is used by the access terminal to trigger a RouteUpdate in the

Connected State. The access network shall set this field to the pilot
111
3GPP2 C.P0087-0 v0.83
detection threshold, expressed as an unsigned binary number equal to 2 10 log10 Ec/I0 . The value used by the access terminal is 0.5 dB
times the value of this field. The access terminal shall support all the
valid values specified by this field.
1
2
3
4
PilotDrop
This value is used by the access terminal to start a pilot drop timer for a
pilot in the Active Set or the Candidate Set. The access network shall set
this field to the pilot drop threshold, expressed as an unsigned binary
number equal to - 2 10 log10 Ec/I0 . The value used by the access
terminal is 0.5 dB times the value of this field. The access terminal
shall support all the valid values specified by this field.
5
6
7
8
9
10
PilotCompare
Active Set versus Candidate Set comparison threshold, expressed as a 2s

complement number. The access terminal transmits a RouteUpdate
message when the strength of a pilot in the Candidate Set exceeds that
of a pilot in the Active Set by this margin. The access network shall set
this field to the threshold Candidate Set pilot to Active Set pilot ratio, in
units of 0.5 dB. The access terminal shall support all the valid values
specified by this field.
11
12
13
14
15
16
17
PilotDropTimer
18
19
20
21
22
23
24
25
26
Table 5.4.7.2.2-21. Pilot Drop Timer Values
27
Timer value after which an action is taken by the access terminal for a
pilot that is a member of the Active Set or Candidate Set, and whose
strength has not become greater than the value specified by PilotDrop. If
the pilot is a member of the Active Set, a RouteUpdate message is sent in
the Connected State. If the pilot is a member of the Candidate Set, it will
be moved to the Neighbor Set. The access network shall set this field to
the drop timer value shown in Table 5.4.7.2.2 -21 corresponding to the
pilot drop timer value to be used by access terminals. The access
terminal shall support all the valid values specified by this field.
PilotDropTimer
Timer
Expiration
(seconds)
PilotDropTimer
Timer
Expiration
(seconds)
< 0.1
27
39
10
55
11
79
12
112
13
159
13
14
225
19
15
319
112
3GPP2 C.P0087-0 v0.83
DynamicThresholds This field shall be set to 1 if the following three fields are included in
2
this record. Otherwise, this field shall be set to 0.
1
SoftSlope
This field shall be included only if DynamicThresholds is set to 1. This

field shall be set to an unsigned binary number, which is used by the
access terminal in the inequality criterion for adding a pilot to the Active
Set or dropping a pilot from the Active Set. The access terminal shall
3
4
5
6
7
AddIntercept

field shall be set to a 2s complement signed binary number in units of
dB. The access terminal shall support all the valid values specified by
this field.
8
9
10
11
DropIntercept
12
13
14
15
NeighborMaxAge
16
17
18
19
Reserved

this field.
The access network shall set this field to the maximum AGE value
beyond which the access terminal is to drop members from the Neighbor
this field.
ignore this field. The length of this field shall be such that the attribute
value record is octet-aligned.
20
21
22
5.4.7.2.3 SetManagementDifferentChannelParameters Attribute
23
The access terminal shall use these attributes if the pilot being compared is on a channel that
25is different from the active set pilots channel.
24
26
Field
Length (bits)
Default Value
Length
N/A
AttributeID
N/A

{
ValueID
N/A
PilotAdd
0x0e
PilotCompare
0x05
PilotDrop
0x12
113
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
Default Value
PilotDropTimer
DynamicThresholds
SoftSlope
0 or 6
N/A
AddIntercept
0 or 6
N/A
DropIntercept
0 or 6
N/A
NeighborMaxAge
Reserved
variable
N/A
}
Length
1
2
3
field.
AttributeID
ValueID
5
6
7
PilotAdd
8
9
10
11
12
13
PilotDrop
14
15
16
17
18
19
PilotCompare
20
21
22
23
24
25
26
This value is used by the access terminal to trigger a RouteUpdate in the

Connected State. The access network shall set this field to the pilot
detection threshold, expressed as an unsigned binary number equal to 2 10 log10 Ec/I0 . The value used by the access terminal is 0.5 dB
times the value of this field. The access terminal shall support all the
valid values specified by this field.
This value is used by the access terminal to start a pilot drop timer for a
pilot in the Active Set or the Candidate Set. The access network shall set
this field to the pilot drop threshold, expressed as an unsigned binary
number equal to - 2 10 log10 Ec/I0 . The value used by the access
terminal is 0.5 dB times the value of this field. The access terminal
shall support all the valid values specified by this field.
Active Set versus Candidate Set comparison threshold, expressed as a 2s
complement number. The access terminal transmits a RouteUpdate
message when the strength of a pilot in the Candidate Set exceeds that
of a pilot in the Active Set by this margin. The access network shall set
this field to the threshold Candidate Set pilot to Active Set pilot ratio, in
units of 0.5 dB. The access terminal shall support all the valid values
specified by this field.
114
3GPP2 C.P0087-0 v0.83
PilotDropTimer
1
2
3
4
5
6
7
8
9
Timer value after which an action is taken by the access terminal for a
pilot that is a member of the Active Set or Candidate Set, and whose
strength has not become greater than the value specified by PilotDrop. If
the pilot is a member of the Active Set, a RouteUpdate message is sent in
the Connected State. If the pilot is a member of the Candidate Set, it will
be moved to the Neighbor Set. The access network shall set this field to
the drop timer value shown in Table 5.4.7.2.2 -21 corresponding to the
pilot drop timer value to be used by access terminals. The access
terminal shall support all the valid values specified by this field.
DynamicThresholds This field shall be set to 1 if the following three fields are included in
this record. Otherwise, this field shall be set to 0.
10
11
SoftSlope

field shall be set to an unsigned binary number, which is used by the
access terminal in the inequality criterion for adding a pilot to the Active
Set or dropping a pilot from the Active Set. The access terminal shall
12
13
14
15
16
AddIntercept

this field.
17
18
19
20
DropIntercept
21
22
23
24
NeighborMaxAge
25
26
27
28
Reserved

this field.
The access network shall set this field to the maximum AGE value
beyond which the access terminal is to drop members from the Neighbor
this field.
ignore this field. The length of this field shall be such that the attribute
value record is octet-aligned.
29
30
31
5.4.7.2.4 SupportedCDMAChannels Attribute
32
The access terminal uses this attribute to convey to the access network the CDMA Channels
supported by the access terminal.
33
34
35
Field
Length (bits)
Default Value
Length
N/A
AttributeID
N/A
115
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
Default Value

{
ValueID
N/A
BandClassCount
BandClassCount occurrences of the following record:

{
BandClass
N/A
BandSubClassCount
N/A
BandSubClassCount occurrences of the following field:

BandSubClass
N/A
07
(as needed)
N/A
}
Reserved
}
Length
1
2
3
Length of the complex attribute in octets. The access terminal shall set
field.
AttributeID
ValueID
access terminal shall set this field to an identifier assigned to this
complex value.
5
6
7
BandClassCount
8
9
BandClass
10
11
The access terminal shall set this field to the number of occurrences of
the BandClass field in this complex value.
The access terminal shall set this field to the band class supported by
the access terminal.
BandSubClassCount The access terminal shall set this field to the number of band subclasses supported by the access terminal in this band class.
12
13
BandSubClass
14
15
Reserved
16
17
The access terminal shall set this field to the band sub-class supported
by the access terminal.
The access terminal shall add reserved bits to make the length of each
attribute value record equal to an integer number of octets. The access
116
3GPP2 C.P0087-0 v0.83
terminal shall set this field to zero. The access network shall ignore this
field.
1
2
3
4
Constant
Meaning
Value
NRUPType
Table 2.5.4-1
of [1]
NRUPDefaultNRUPInterR
0x00000x00
02
NRUPActive
Maximum size of the Active Set
NRUPCandidate
Maximum size of the Candidate Set
NRUPNeighbor
Minimum size of the Neighbor Set
20
AT
The Session State Information record (see 14.8 of [1]) consists of parameter records.
This protocol defines the following parameter record in addition to the configuration attributes
for this protocol.
7
8
5.4.9.1 RouteUpdate Parameter
The following parameter shall be included in the Session State Information record only if the
Session State Information is being transferred while the connection is open.
10
11
12
Field
Length (bits)
ParameterType
Length
TCAMessageSequence
RUPMessageSequence
ChannelIncluded
Channel
0 or 24
FrameOffset
DRCLength
DRCChannelGainBase
ACKChannelGain
NumPilots
117
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
NumPilots occurrences of the following fields

PilotPN
SectorID
128
SofterHandoff
MACIndexLSBs
DRCCover
RABLength
RABOffset
Reserved
Variable
ParameterType
Length
2
3
TCAMessageSequence
5
6
TrafficChannelAssignment message that was sent by the source access
7
network.
4
RUPMessageSequence
9
10
RouteUpdate message that was received by the source access network.
8
ChannelIncluded
11
12
13
Channel
14
15
16
17
FrameOffset
18
19
20
DRCLength
21
22
23
This field shall be set to the ChannelIncluded field in the last

network.
This field shall be included only if the ChannelIncluded field is set to 1.
If included, this field shall be set to the last Channel field of the last
network.
This field shall be set to the FrameOffset field in the last
network.
This field shall be set to the DRCLength field in the last
network.
118
3GPP2 C.P0087-0 v0.83
DRCChannelGainBase
2
3
4
ACKChannelGain
5
6
7
NumPilots
8
9
10
PilotPN
11
12
13
SectorID
14
15
SofterHandoff
16
17
18
MACIndexLSBs
19
20
21
DRCCover
22
23
24
RABLength
25
26
27
RABOffset
28
29
30
Reserved
31
32
33
This field shall be set to the DRCChannelGainBase field in the last

network.
This field shall be set to the ACKChannelGain field in the last
network.
This field shall be set to the NumPilots field in the last
network.
This field shall be set to the corresponding PilotPN field in the last
network.
This field shall be set to the SectorID corresponding to the sector
associated with the PilotPN specified above.
This field shall be set to the corresponding SofterHandoff field in the last
network.
This field shall be set to the corresponding MACIndexLSBs field in the
last TrafficChannelAssignment message that was sent by the source
access network.
This field shall be set to the corresponding DRCCover field in the last
network.
This field shall be set to the corresponding RABLength field in the last
network.
This field shall be set to the corresponding RABOffset field in the last
network.
the length of this parameter record length an integer number of octets.
This field shall be set to all zeros.
119
3GPP2 C.P0087-0 v0.83
5.4.9.2 ExtendedRouteUpdate Parameter
The following parameter shall be included in the Session State Information record only if the
3Session State Information is being transferred while the connection is open, and if
4MACIndexMSB fields were included in the last TrafficChannelAssignment message that was
5sent by the source access network.
2
6
7
Parameter
Field
Length (bits)
ParameterType
Length
NumPilots

MACIndexMSB
DSCChannelGain
NumCells
NumCells occurrences of the following field:

DSC
Reserved
0 7 (as needed)
ParameterType
Length
9
10
NumPilots
11
12
13
MACIndexMSB
14
15
16
DSCChannelGain
17
18
19
This field shall be set to the NumPilots field in the last

network.
This field shall be set to the corresponding MACIndexMSB field in the
last TrafficChannelAssignment message that was sent by the source
access network.
This field shall be set to the DSCChannelGain field in the last
network.
120
3GPP2 C.P0087-0 v0.83
NumCells
1
2
3
DSC
4
5
6
Reserved
7
8
9
This field shall be set to the number of DSC fields included in the last
network.
This field shall be set to the corresponding DSC field in the last
network.
the length of this parameter record length an integer number of octets.
This field shall be set to all zeros.
5.4.9.3 AttributeOverrideMessageSequence Parameter
10
The following parameter shall be included in the Session State Information Record only if the
Session State Information is being transferred while the Connection is open and
13SetManagementOverrideAllowed is set to 0x01.
11
12
14
15
Table 5.4.9.3-1. The Format of the Parameter Record for the

AttributeOverrideMessageSequence Parameter
Field
Length
(bits)
ParameterType
Length
AttributeOverrideMessageSequence
ParameterType
Length
16
17
18
AttributeOverrideMessageSequence
21
AttributeOverride message that was sent by the source access network. If
22
the access network has not sent the AttributeOverride message during
23
this connection, then this field shall be set to 255.
19
20
24
25
121
3GPP2 C.P0087-0 v0.83
5.5 Inter-RAT Overhead Messages Protocol
5.5.1 Overview
The QuickConfig message and the SectorParameters message are collectively termed the
5overhead messages. These messages are broadcast by the access network over the Control
6Channel. These messages are unique, in that they pertain to multiple protocols and are,
7therefore, specified separately. The Overhead Messages Protocol provides procedures related to
8transmission, reception and supervision of these messages. The Inter-RAT Overhead Messages
9Protocol also defines HRPD Silence Parameters for supporting active handoff from other radio
10access technologies.
4
This protocol can be in one of three states:
11
12
13
14
15
16
17
18
19
Inactive State: In this state, the protocol waits for an Activate command. This state
corresponds only to the access terminal and occurs when the access terminal has not
acquired an access network or is not required to receive overhead messages.
Active State: In this state the access network transmits and the access terminal receives
overhead messages.
Tunnel Active State: In this state the access terminal operates in the Inter-RAT tunnel
mode (e.g. E-UTRAN tunnel mode) . The access terminal receives HRPD overhead
parameters needed for tunnel mode operation through source RAT (e.g. E-UTRAN).
20
Initial State
(AT)
Initial State
(AN)
Activate
(AT Only)
Active State
Inactive State
Deactivate
(AT only)
Activate
(Tunnel Mode)
(AT Only)
Deactivate(AT Only)
TunnelDeactivate
(AT only)
Tunnel Active
State
21
22
Figure 5.5.1-13. Inter-RAT Overhead Messages Protocol State Diagram
23
5.5.2.1 Commands
24
25
122
3GPP2 C.P0087-0 v0.83
Activate
Deactivate
TunnelDeactivate
ANRedirected
SupervisionFailed
Updated
5.5.2.3 Public Data
10
11
12
All data in the overhead messages50
13
OverheadParametersUpToDate
14
15
16
18
19
20
21
22
23
24
25
26
27
28
50 The HRPD neighbor list parameters received during the Tunnel Active State is stored in the existing
3neighbor
4HRPD
5The
6as
list public data structure as specified by the overhead message. The procedure of storing the
neighbor list parameters received during the Tunnel Active State is specified in section 5.5.6.1.5.
parameters of received HRPDSilenceParameters message during the Tunnel Active State also store
the public data.
123
3GPP2 C.P0087-0 v0.83
1
2
that attribute.
4
The protocol at the access terminal shall enter the Inactive State.
The protocol at the access network shall enter the Active State.
10
The protocol shall set HRPDPreRegistrationAllowed to 0.
11
5.5.5.1 Procedures
12
This protocol uses the Generic Configuration Protocol (see 14.7 of [1]) to define the processing
14of the configuration messages.
13
15
16
20
subtype as the corresponding InConfiguration protocol instance, then
21
instances of the Overhead Messages protocol to the Inactive State.
instances of the Overhead Messages protocol to the Active State.
19
22
23
24
26
27
28
the protocol.
25
29
30
31
32
34
instance, then the access terminal and the access network shall perform the following:
35
33
36
Overhead Messages Protocol at the access terminal and the access network.
124
3GPP2 C.P0087-0 v0.83
1
2
InUse protocol.
5
6
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
The
sender
shall
increment
8
9
AttributeRecord
10
this
value
for
each
new
11
Channels
FTC
Addressing
SLP
RTC
Reliable
Priority
unicast
40
12
13
14
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
15
16
17
125
3GPP2 C.P0087-0 v0.83
AttributeRecord
1
2
3
4
5
6

Channels
Addressing
FTC
RTC
unicast
SLP
Reliable
Priority
40
5.5.6.1 Procedures
5.5.6.1.1 Extensibility Requirements
Further revisions of the access network may add new overhead messages.
10
The access terminal shall discard overhead messages with a MessageID field it does not
12recognize.
11
Further revisions of the access network may add new fields to existing overhead messages.
These fields shall be added to the end of the message, prior to the Reserved field if such a field
15is defined.
13
14
The access terminal shall ignore fields it does not recognize.
16
17
The access network shall ignore all commands.
18
19
If this protocol receives an Activate command in the Inactive State:
20
23
The access terminal shall transition to the Active State if TunnelModeEnabled, as public
data of SingalingSignaling Adaptation ProtoclProtocol, is set to 0. The access terminal
shall transition to the Tunnel Active State if TunnelModeEnabled is set to 1.
24
The access network shall ignore it.
21
22
If this protocol receives the command in the Active State, it shall be ignored.
25
26
If this protocol receives a Deactivate command in the Inactive State, it shall be ignored.
27
If this protocol receives the command in the Active State or in the Tunnel Active State:
28
30
Access terminal shall set HRPDPreRegistrationAllowed to 0 and transition to the Inactive

State.
31
Access network shall ignore it.
29
126
3GPP2 C.P0087-0 v0.83
5.5.6.1.2.3 TunnelDeactivate
If this protocol receives a TunnelDeactivate command in the Inactive State or in the Active
3State, it shall be ignored.
2
If this protocol receives the command in the Tunnel Active State:
Set OverheadParametersUpToDate to 0 and HRPDPreRegistrationAllowed to 0.
The access terminal shall transition to the Active State.
The access network shall ignore it.
This state corresponds only to the access terminal and occurs when the access terminal has
10not acquired an access network or is not required to receive overhead messages. In this state,
11the protocol waits for an Activate command.
9
5.5.6.1.4 Active State
12
13
The access network shall include a QuickConfig message in every Control Channel
15synchronous Sleep State capsule. The access network should include a SectorParameters
16message in the synchronous capsule at least once every N OMPSectorParameters Control Channel cycles.
17The access network shall set the SectorSignature field of the QuickConfig message to the
18SectorSignature field of the next SectorParameters message. The access network shall set the
19AccessSignature field of the QuickConfig message to the public data AccessSignature (see
20Access Channel MAC Protocol).
14
21
When in the Active State, the access terminal shall perform supervision on the QuickConfig
and the SectorParameters messages as specified in 5.5.6.1.4.2.1.1 and 5.5.6.1.4.2.1.2,
24respectively.
22
23
If the access terminal does not have any stored value for the overhead parameters or if it
receives a RouteUpdate.IdleHO indication, or if it receives a ConnectedState.ConnectionClosed
27indication, the access terminal shall set OverheadParametersUpToDate to 0.
25
26
When the access terminal receives the QuickConfig message, it shall perform the following:
28
29
If any of the following conditions are true:
30
OverheadParametersUpToDate is equal to 0,
31
the value of the SectorSignature field of the new QuickConfig message is different from
the last received value for SectorSignature corresponding to the same sector 51 from
which the QuickConfig message is received, or
32
33
51 A sector is specified by its SectorID and the CDMA channel associated with it (see the definition of
3Sector).
127
3GPP2 C.P0087-0 v0.83
the sector from which this QuickConfig message is received is different from the sector
from which the last QuickConfig message was received,
then the access terminal shall perform the following:
The access terminal shall set OverheadParametersUpToDate to 0.
The access terminal shall monitor every subsequent Control Channel synchronous
capsule until it receives the updated SectorParameters message. When the access
terminal receives the updated SectorParameters message, it shall return an Updated
indication and set OverheadParametersUpToDate to 1.
6
7
8
Once the access terminal receives an updated overhead message, it should store the signature
10associated with the message for future comparisons. The access terminal may cache overhead
11message parameters and signatures to speed up acquisition of parameters from a sector that
12was previously monitored.
9
If the Redirect field of the QuickConfig message is set to 1, the access terminal shall return an
ANRedirected indication 52.
13
14
The access terminal shall store a list of RouteUpdateTriggerCodes associated with subnets
16visited by the access terminal for future comparisons and for future use. This list is called the
17RouteUpdateTriggerCodeList. Each entry in the RouteUpdateTriggerCodeList shall include the
18subnet and the RouteUpdateTriggerCode. Other protocols may cache information keyed by
19(Subnet, RouteUpdateTriggerCode) pairs. If other protocols cache information keyed by (Subnet,
20RouteUpdateTriggerCode) pairs, then these protocols shall delete such information when the
21(Subnet, RouteUpdateTriggerCode) pair is deleted from the RouteUpdateTriggerCodeList.
15
If RouteUpdateTriggerCodeListSize is set to 0x00, the access terminal shall delete all entries in
23the RouteUpdateTriggerCodeList. Otherwise, the access terminal shall perform the following:
22
24
25
26
27
28
29
30
31
32
The access terminal shall delete any entries in the RouteUpdateTriggerCodeList other than
the current (Subnet, RouteUpdateTriggerCode) received in the most recent
SectorParameters message if the entries have an expiration timer that has been running for
at least 2^(RouteUpdateTriggerMaxAge + 3) 1.28 seconds.
If the expiration timer for the RouteUpdateTriggerCodeList entry corresponding to the
current (Subnet, RouteUpdateTriggerCode) received in the most recent SectorParameters
message has been running for at least 2^(RouteUpdateTriggerMaxAge + 3) 1.28 seconds,
the access terminal shall reset, initialize to zero, and restart the expiration timer for that
entry.
52 Redirection is commonly used in networks under test.
128
3GPP2 C.P0087-0 v0.83
1
2
3
4
5
6
7
8
9
If the (Subnet, RouteUpdateTriggerCode) pair from the most recently received

SectorParameters message is not included in the RouteUpdateTriggerCodeList, then the
access terminal shall add the entry to the RouteUpdateTriggerCodeList and shall reset,
initialize to zero, and start the expiration timer for that entry 53. The access terminal shall
generate a RouteUpdate.SendRouteUpdate command when it adds an entry to the
RouteUpdateTriggerCodeList. If there are more than the number of entries specified by the
RouteUpdateTriggerCodeListSize attribute in the RouteUpdateTriggerCodeList, then the
access terminal shall delete entries from the list until there are exactly
RouteUpdateTriggerCodeListSize entries in the list according to the following rules:
10
The access terminal shall delete the oldest entries in the list first, and
11
the access terminal shall not delete the entry in the list that corresponds to the
(Subnet, RouteUpdateTriggerCode) received in the most recent SectorParameters
message.
12
13
5.5.6.1.4.2.1 Supervision Procedures
14
5.5.6.1.4.2.1.1 Supervision of QuickConfig Message
15
Upon entering the Active State, the access terminal shall start the following procedure to
17supervise the QuickConfig message:
16
The access terminal shall set a QuickConfig supervision timer for TOMPQCSupervision.
18
If a QuickConfig message is received while the timer is active, the access terminal shall reset
and restart the timer.
19
20
If the timer expires, the access terminal shall return a SupervisionFailed indication and disable
22the timer.
21
5.5.6.1.4.2.1.2 Supervision of SectorParameters Message
23
Upon entering the Active State, the access terminal shall start the following procedure to
25supervise the SectorParameters message:
24
The access terminal shall set a SectorParameters supervision timer for T OMPSPSupervision.
26
If a SectorParameters message is received while the timer is active, the access terminal shall
reset and restart the timer.
27
28
If a QuickConfig message is received while the timer is active and the SectorSignature field of
30the QuickConfig message matches the last received value for SectorSignature corresponding to
54
31the same sector
from which the QuickConfig message is received, the access terminal shall
32reset and restart the timer.
29
53
The access terminal could choose to wait for confirmation that the RouteUpdate was
delivered before updating the RouteUpdateTriggerCode list.
2
3
54 A sector is specified by its SectorID and the CDMA channel associated with it (see the definition of
5Sector).
129
3GPP2 C.P0087-0 v0.83
If the timer expires, the access terminal shall return a SupervisionFailed indication and disable
2the timer.
1
5.5.6.1.5 Tunnel Active State
Not applicable to Access Network.
If the access terminal does not have any stored value for the overhead parameters or if it
8receives an indication that the E-UTRAN protocol within the access terminal selected a
55
9new serving cell , the access terminal shall set OverheadParametersUpToDate to 0. If the new
10serving cell allows the access terminal to perform pre-registration, then the access terminal
11shall
set HRPDPreRegistrationAllowed to 1; otherwise, the access terminal shall set
12HRPDPreRegistrationAllowed to 0.
7
When the access terminal receives the HRPD neighbor list parameters, it shall perform the
following:
13
14
15
If any of the following conditions are true:
16
OverheadParametersUpToDate is equal to 0,
17
Access terminal determine that HRPD parameters, defined as public data of this
application, received from different RAT 56 (e.g. E-UTRAN) is not up-to-date57
18
19
then the access terminal shall perform the following:
20
21
The access terminal shall store the following HRPD neighbor list parameters received
[11]]:
22
Set ColorCode to HRPDPreRegistrationZoneID received from E-UTRAN.
23
Set SecondaryColorCode to HRPDSecondaryPreRegistrationZoneID received from EUTRAN
If the HRPD neighbor list is also received:
24
25
26
27
HRPD search window size if included. The received HRPD search window size
is common for all the neighbor pilot PNs in the received HRPD neighbor list
55 The process by which the E-UTRAN protocol within the access terminal communicates this event to
4the
Overhead Messages Protocol is left to the access terminal implementation.
56 The access terminal may receive HRPD neighbor list information from E-UTRAN [11].
6neighbor
list
information
7MeasObjectCDMA2000
may
be
included
in
either
the
received
SIB8
or
The HRPD
the
received
information element.
57 For example, when access terminal camp on the primary RAT is E-UTRAN, the access terminal can
9determine
the broadcast information is not up-to-date based on the TAG [11] value, difference in the
10received
SIB8 (e.g. HRPD-NeighborCellList) or based on the HRPD neighbor list difference between the
11received
SIB8 and MeasObjectCDMA2000 IE [11].
12
130
3GPP2 C.P0087-0 v0.83
HRPD neighbor pilot PNs
Set SystemType field of the NeighborChannel corresponding to each received

HRPD neighbor pilot PN to 0x00 [14.1 of [1]]
HRPD neighbor band class information as the BandClass [14.1 of [1]] field of
the NeighborChannel corresponding to each received HRPD neighbor pilot PN
HRPD neighbor channel number as the ChannelNumber [14.1 of [1]] field of the
NeighborChannel corresponding to each received HRPD neighbor pilot PN
3
4
5
6
7
8
The access terminal return an Updated indication
The access terminal set OverheadParametersUpToDate to 1.
Upon receiving an HRPDSilenceParameters message, the access terminal shall overwrite the
stored value of ReverseLinkSilenceDuration and ReverseLinkSilencePeriod fields of every
12stored
SectorParameters message with the
ReverseLinkSilenceDuration
and
13ReverseLinkSilencePeriod fields of the message.
10
11
14
5.5.6.2.1 QuickConfig
15
The QuickConfig message is used to indicate a change in the overhead messages contents and
17to provide frequently changing information.
16
18
131
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
ColorCode
SectorID24
24
SectorSignature
16
AccessSignature
16
Redirect
RPCCount63To0
RPCCount63To0 occurrences of the following field

ForwardTrafficValid63To0
RPCCount127To64Included
0 or 1
RPCCount127To64
0 or 6
RPCCount127To64 occurrences of the following field:

0 or 1
Reserved
0 7 (as needed)
MessageID
ColorCode
The access network shall set this field to the color code corresponding to
this sector.
2
3
SectorID24
4
5
SectorSignature
6
7
AccessSignature
8
9
10
Redirect
11
12
The access network shall set this field to the least significant 24 bits of
the SectorID value corresponding to this sector.
The access network shall set this field to the value of the SectorSignature
field of the next SectorParameters message it will transmit.
AccessSignature parameter from the AccessParameters message that is
Public Data of the Access Channel MAC Protocol.
Access network redirect. The access network shall set this field to 1 if it
is redirecting all access terminals away from this access network58.
58 Network redirect is commonly used during testing.
132
3GPP2 C.P0087-0 v0.83
RPCCount63To0
1
2
3
The access network shall set this field to the maximum number of RPC
channels supported by the sector corresponding to Forward Traffic
Channels associated with MAC indices 0 through 63, inclusive.
The access network shall set occurrence n of this field to 1 if the

Forward Traffic Channel associated with MACIndex 64-n is valid. The
access terminal uses this field to perform supervision of the Forward
Traffic Channel.
5
6
7
8
If this field is included, the access network shall set this field to 1 if the
RPCCount127To64 field is included in this message. Otherwise, the
10
11
12
RPCCount127To64
13
14
15
16
17
18
If
the
field
is
omitted,
or
if
RPCCount127To64Included is 0, then the access network shall omit
this field. Otherwise, the access network shall set this field to the
maximum number of RPC channels supported by the sector
corresponding to Forward Traffic Channels associated with MAC indices
64 through 127, inclusive.
19
If
the
field
is
omitted,
or
if
RPCCount127To64Included is 0, then the access network shall omit
this field. Otherwise, the access network shall set occurrence n of this
field to 1 if the Forward Traffic Channel associated with MACIndex 128n is valid. The access terminal uses this field to perform supervision of
the Forward Traffic Channel.
20
21
22
23
24
25
Reserved
26
27
28
29
Channels
CCsynSS
SLP
Addressing
broadcast
Priority
Best
Effort
10
5.5.6.2.2 SectorParameters
30
The SectorParameters message is used to convey sector specific information to the access
terminals.
31
32
33
133
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
CountryCode
12
SectorID
128
SubnetMask
SectorSignature
16
Latitude
22
Longitude
23
RouteUpdateRadiusOverhead
11
LeapSeconds
LocalTimeOffset
11
ReverseLinkSilencePeriod
ChannelCount
ChannelCount occurrences of the following field:

Channel
24
NeighborCount
NeighborCount occurrences of the following field:

NeighborPilotPN
NeighborCount occurrences of the following two fields:

NeighborChannel
0 or 24
NeighborSearchWindowSizeIncluded
NeighborCount occurencesoccurrences of the

following field
NeighborSearchWindowSize
0 or 4
NeighborSearchWindowOffsetIncluded
NeighborCount occurrences of the following field
134
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
NeighborSearchWindowOffset
0 or 3
ExtendedChannelIncluded
0 or 1
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),
AccessHashingChannelMaskSameAsP
revious
AccessHashingChannelMask
0 or
AccessHashi
ngMaskLengt
h+1
RouteUpdateTriggerCodeIncluded
0 or 1
RouteUpdateTriggerCode
0 or 12
RouteUpdateTriggerMaxAge
0 or 4
PriorSessionGAUP
0 or 1
0 or 1
m, 0 m NeighborCount occurrences of the

following field:
FPDCHSupported
0 or 1
SecondaryColorCodeIncluded
0 or 1
SecondaryColorCodeCount
0 or 3
Zero or SecondaryColorCodeCount occurrences of the

following field:
SecondaryColorCode
135
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
0 7 (as
needed)
Reserved
MessageID
CountryCode
The access network shall set this field to the three-digit BCD (binary
coded decimal) encoded representation of the Mobile Country Code (as
specified in [10]) associated with this sector.
2
3
4
SectorID
5
6
7
8
9
SubnetMask
10
11
12
13
SectorSignature
14
15
Latitude
16
17
18
19
20
21
Longitude
22
23
24
25
26
27
Sector Address Identifier. The Access Network shall set the value of the
SectorID according to the rules specified in 14.9 of [1]. The access
terminal shall not assume anything about the format of the SectorID
other than the (SectorID, CDMA Channel) pair uniquely identifies a
sector.
Sector Subnet identifier. The access network shall set this field to the
number of consecutive 1's in the subnet mask of the subnet to which
this sector belongs. The value of this field should be less than or equal to
104 if SecondaryColorCodeIncluded field is included and is set to 1.
SectorParameters message signature. The access network shall change
this field if the contents of the SectorParameters message changes.
The latitude of the sector. The access network shall set this field to this
sectors latitude in units of 0.25 second, expressed as a twos
complement signed number with positive numbers signifying North
latitudes. The access network shall set this field to a value in the range
-1296000 to 1296000 inclusive (corresponding to a range of -90 to
+90).
The longitude of the sector. The access network shall set this field to this
sectors longitude in units of 0.25 second, expressed as a twos
complement signed number with positive numbers signifying East
longitude. The access network shall set this field to a value in the range
-2592000 to 2592000 inclusive (corresponding to a range of -180 to
+180).
RouteUpdateRadiusOverhead
29
If the access terminal is to perform distance based route updates, the
30
access network shall set this field to the non-zero distance beyond
31
which the access terminal is to send a new RouteUpdate message (see
32
Inter-RAT Route Update Protocol). If access terminals are not to perform
28
136
3GPP2 C.P0087-0 v0.83
distance based route updates, the access network shall set this field to
059.
1
2
LeapSeconds
3
4
LocalTimeOffset
5
6
7
The number of leap seconds that have occurred since the start of CDMA
System Time.
The access network shall set this field to the offset of the local time from
CDMA System Time. This value will be in units of minutes, expressed as
a twos complement signed number.
The access network shall set this field to specify the duration of the
10
Reverse Link Silence Interval in units of frames.
8
9
12
The access network shall set this field to specify the period of the Reverse
13
Link Silence Interval. The Reverse Link Silence Interval is defined as the
14
time interval of duration ReverseLinkSilenceDuration frames that starts
15
at times T where T is the CDMA System Time in units of frames and it
16
satisfies the following equation:
11
T mod (20482ReverseLinkSilencePeriod - 1) = 0.
17
ChannelCount
18
19
Channel
20
21
22
NeighborCount
23
24
NeighborPilotPN
25
26
The access network shall set this field to the number of cdma2000 high
rate packet data channels available to the access terminal on this sector.
Channel record specification for each channel. See 14.1 of [1] for the
Channel record format. The access network shall set the SystemType
field of this record to 0x00.
The access network shall set this field to the number of records
specifying neighboring sectors information included in this message.
sector that the access terminal should add to its Neighbor Set.
The access network shall set this field to 1 if a Channel record is
29
included for this neighbor, and to 0 otherwise. The nth occurrence of
30
this field corresponds to the nth occurrence of NeighborPilotPN in the
31
record that contains the NeighborPilotPN field above.
27
28
59 The access terminal determines whether to send a distance based RouteUpdate message or not using
3the
RouteUpdateRadiusOverhead value of the serving sector. If the serving sector allows distance based
4Route
Updates, the access terminal uses the RouteUpdateRadiusOverhead value sent by the sector in
5which
the access terminal last registered.
137
3GPP2 C.P0087-0 v0.83
NeighborChannel
1
2
3
4
5
6
Channel record specification for the neighbor channel. See 14.1 of [1] for
the Channel record format. The access network shall omit this field if the
corresponding NeighborChannelIncluded field is set to 0. Otherwise, if
included, the nth occurrence of this field corresponds to the nth
occurrence of NeighborPilotPN in the record that contains the
NeighborPilotPN field above.
8
The
access
network
shall
set
this
field
to
1
if
9
NeighborSearchWindowSize field for neighboring sectors is included in
10
7
NeighborSearchWindowSize
12
The
access
network
shall
omit
this
field
if
13
is
set
to
0.
If
14
NeighborSearchWindowSizeIncluded is set to 1, the access network
15
16
to the search window size to be used by the access terminal for the
17
18
19
11
138
3GPP2 C.P0087-0 v0.83
Table 5.5.6.2-24. Search Window Sizes

Search Window Size

(PN chips)
10
14
20
28
40
60
80
10
100
11
130
12
160
13
226
14
320
15
452
The
access
network
shall
set
this
field
to
1
if
4
NeighborSearchWindowOffset field for neighboring sectors is included in
5
2
3
NeighborSearchWindowOffset
The
access
network
shall
omit
this
field
if
8
is
set
to
0.
If
9
NeighborSearchWindowOffsetIncluded is set to 1, the access network
10
11
to the search window offset to be used by the access terminal for the
12
13
14
6
7
139
3GPP2 C.P0087-0 v0.83
Table 5.5.6.2-25. Search Window Offset
SearchWindowOffset
Offset ( PN chips)
WindowSize 60 /2
WindowSize
3 WindowSize /2
- WindowSize /2
- WindowSize
-3 WindowSize /2
Reserved
ExtendedChannelIncluded
3
If any of the fields after this field except for Reserved are included, the
4
access network shall include this field. Otherwise, the access network
5
shall omit this field. If included, the access network shall set this field as
6
follows:
2
7
8
9
10
The access network shall set this field to 0 if the ExtendedChannel

1.
ExtendedChannelCount
If the ExtendedChannelIncluded field is omitted or is included and set to
13
0, the access network shall omit this field. Otherwise, the access
14
network shall include this field and shall set this field to the number of
15
cdma2000 high rate packet data extended channels available to the
16
access terminal on this sector. If this field is not included, the access
17
terminal shall assume that the value of this field is 00000.
11
12
ExtendedChannel
18
19
20
21
Channel record specification for each extended channel. If

ExtendedChannelCount is not included, the access network shall omit
this field. See 14.1 of [1] for the Channel record format. The access
network shall set the SystemType field of this record to 0x00.
AccessHashingChannelMaskIncluded
23
If any of the fields after this field except for Reserved are included, the
24
access network shall include this field. Otherwise, the access network
25
shall omit this field. If included, the access network shall set this field as
26
follows:
27
The
access
network
shall
set
this
field
to
0
if
the
22
140
3GPP2 C.P0087-0 v0.83
1
2
AccessHashingChannelMask fields are omitted. Otherwise, the access

AccessHashingMaskLength
4
If the AccessHashingChannelMaskIncluded field is omitted or is
5
included and set to 0, the access network shall omit this field.
6
Otherwise, the access network shall set this field one less than the
7
number of bits in the AccessHashingChannelMask field(s).
3
If the AccessHashingChannelMaskIncluded field is omitted or is included and set to 0, the

access network shall omit the following two-field record. Otherwise, the access network shall
10include m occurrences of the following two field record, where m is the total number of
11Channel and ExtendedChannel records in this message that have SystemType equal to 0x00
8
9
AccessHashingChannelMaskSameAsPrevious
The access network shall set this field in the ith occurrence of this record
14
as follows:
15
If i is greater than 1 and the AccessHashingChannelMask for the ith
16
Channel or ExtendedChannel record with SystemType equal to 0x00 in
17
this message is the same as the AccessHashingChannelMask for the (i18
1)th Channel or ExtendedChannel record with SystemType equal to 0x00
19
in this message, the access network may set this field to 1. Otherwise,
20
the access network shall set this field to 0.
12
13
AccessHashingChannelMask
22
The access network shall set this field in the ith occurrence of this record
23
as follows:
24
If the AccessHashingChannelMaskSameAsPrevious field in this record is
25
set to 1, the access network shall omit this field. Otherwise, the access
26
network shall set this field to the (AccessHashingMaskLength + 1) bit
27
access hashing class of the ith combined channel list entry in this
28
message that has SystemType equal to 0x00, where the combined
29
channel list is defined to be the ordered set of all Channel records in
30
order (if any) with all Extended Channel records appended in order (if
31
any). If this field is not included, the access terminal shall assume that
32
the value of this field is the same as the value for this field in the
33
previous occurrence of this record.
21
RouteUpdateTriggerCodeIncluded
The access network shall include this field if any of the fields other than
36
the Reserved field that follow this field are to be included in the message.
37
If this field is included, the access network shall set it as follows: The
38
access network shall set this field to 1 if RouteUpdateTriggerCode is
39
included in this message. Otherwise, the access network shall set this
40
field to 0.
34
35
141
3GPP2 C.P0087-0 v0.83
RouteUpdateTriggerCode
2
If the RouteUpdateTriggerCodeIncluded field is not included in this
3
message, or if the RouteUpdateTriggerCodeIncluded field is included and
4
is set to 0, then the access network shall omit this field. Otherwise, the
5
access network shall set this field to a 12-bit value 61.
1
RouteUpdateTriggerMaxAge
If the RouteUpdateTriggerCodeIncluded field is not included in this
8
message or if the RouteUpdateTriggerCodeIncluded field is included and
9
set to 0, the access network shall omit this field. Otherwise, the access
10
network shall set this field to indicate the duration of the
11
RouteUpdateTriggerCode timer.
6
7
PriorSessionGAUP
12
13
14
15
16
17
18
19
If this field is included, then the access network shall set this field as
follows:
If the access terminal is not allowed to include the PriorSession attribute
in an AttributeUpdateRequest message, then the access network shall
set this field to 0. Otherwise, the access network shall set this field to
1.
The access network shall set this field to 0 if the FPDCHSupported
1.
20
21
22
23
24
25
26
FPDCHSupported
27
28
29
30
31
32
33
34
35
36
If FPDCHSupportedIncluded is not included or is included and is set to

0, then the access network shall omit all occurrences of this field.
Otherwise, the access network shall include m occurrences of this field,
where m is the number of NeighborChannel records in this message that
have SystemType equal to 0x01, and the access network shall set the
occurrences of this field as follows:
The access network shall set the ith occurrence of this field as follows:
If the system on the CDMA Channel corresponding to the ith
NeighborChannel record that has SystemType equal to 0x01 supports
the Forward Packet Data Channel (see [9]), the access network shall set
61 The RouteUpdateTriggerCode represents parameters associated with other protocols or applications. A
4RouteUpdate
5update
6parameters
message is triggered when the RouteUpdateTriggerCode changes. The access network can
parameters associated with other protocols or applications when it determines that the
at the access terminal need to be updated.
142
3GPP2 C.P0087-0 v0.83
the ith occurrence of this field to 1. Otherwise, the access network

shall set the ith occurrence of this field to 0.
1
2
SecondaryColorCodeIncluded
The access network shall include this field if any of the non-reserved
fields that follow this field are to be included in the message. If included,
the access network shall set this field as follows:
The
access
network
shall
set
this
field
to
1
if
the
SecondaryColorCodeCount field is included. Otherwise, the access
4
5
6
7
8
9
SecondaryColorCodeCount
10
If SecondaryColorCodeIncluded is omitted or set to 0, then the access

network shall omit this field. Otherwise, the access network shall set this
field as follows:
If SecondaryColorCodeIncluded is included and set to 1, then the
access network shall set this field to indicate the number of secondary
color codes covering this sector. If the access terminal is to consider all
possible values of SecondaryColorCode to be included in this message,
then the access network shall set this field to 000.
11
12
13
14
15
16
17
18
SecondaryColorCode
19
If SecondaryColorCodeCount is omitted or included and set to 000,

then the access network shall omit this field. Otherwise, the access
network shall set this field as follows:
The access network shall set this field to a color code that is to be
considered to be a member of the set of the SecondaryColorCode values.
20
21
22
23
24
Reserved
25
26
27
28
Channels
Addressing
SLP
CCsyn
Priority
broadcast
Best
Effort
30
29
5.5.6.2.3 HRPDSilenceParameters
30
The access network sends an HRPDSilenceParameters message as part of the preparation for
32an active handoff from the other radio access technology to HRPD.
31
33
143
3GPP2 C.P0087-0 v0.83
Field
Length (bits)
MessageID
Reserved
0 7 (as needed)
MessageID
The access network shall set this field to specify the duration of the
4
Reverse Link Silence Interval in units of frames.
2
3
6
The access network shall set this field to specify the period of the Reverse
7
Link Silence Interval. The Reverse Link Silence Interval is defined as the
8
time interval of duration ReverseLinkSilenceDuration frames that starts
9
at times T where T is the CDMA System Time in units of frames and it
10
satisfies the following equation:
5
T mod (20482ReverseLinkSilencePeriod - 1) = 0.
11
Reserved
12
13
14
15
Channels
Addressing
SLP
CC
Priority
unicast
16
17
This protocol sends the following command:
18
19
RouteUpdate.SendRouteUpdate
20
21
22
RouteUpdate.IdleHO
23
144
Best
Effort
40
3GPP2 C.P0087-0 v0.83
1
2
The simple configurable attributes are listed in Table 5.5.7 -26. The access network and the
4access terminal shall use the default values that are typed in bold italics.
3
Table 5.5.7-26 Configurable Simple Attributes
Attribute
ID
0xff
0xfe
Attribute
OverheadCachePeriod
RouteUpdateTriggerCod
eListSize
Values
Meaning
0x00
Value of overhead cache period is zero.
0x01 to
0xff
Value of overhead cache period in units of

5.12 seconds.
0x00
Sending of RouteUpdate messages based

on the RouteUpdateTriggerCodeList is
disabled.
0x01
0x05
Size of the RouteUpdateTriggerCodeList
All other
values
Reserved.
7
8
Constant
Meaning
Value
NOMPType
Table 2.5.4-1 of
[1]3.1.2-1
NOMPInterRAT
0x0001
TIROMPQCSupervision
QuickConfig supervision timer
12 Control
Channel cycles
TIROMPSPSupervision
SectorParameters supervision timer
12 Control
Channel cycles
NIROMPSectorParameters
The recommended maximum number of Control

Channel cycles between two consecutive
SectorParameters message transmissions
Information record (see 14.8 of [1])
10
11
145
3GPP2 C.P0087-0 v0.83
1
2
146
3GPP2 C.P0087-0 v0.83
5.6 Default Signaling Adaptation Protocol
5.6.1 Overview
This protocol does not provide any services.
5.6.2.1 Commands
This protocol does not issue any commands.
This protocol does not return any indications.
5.6.2.3 Public Data
10
11
12
This protocol does not define a protocol data unit.
13
14
5.6.4.1 Protocol Initialization for the InConfiguration Instance of the Protocol
15
16
17
18
19
20
21
22
23
24
25
The fall-back values of the attributes for this instance of the protocol shall be set to the
default values specified for each attribute (See [1] for a description of fall-back values).
If the InUse instance of this protocol has the same protocol subtype as that of the
InConfiguration instance of the protocol, then the fall-back values of the attributes defined
by the InConfiguration instance of the protocol shall be set to the values of the
corresponding attributes associated with the InUse instance of the protocol.
The value for each attribute for this instance of the protocol shall be set to the fall-back
value for that attribute.
5.6.4.2 Protocol Initialization for the InUse Instance of the Protocol
26
Upon creation of the InUse instance of this protocol, the access terminal and the access
27
29
30
The value of the attributes for this instance of the protocol shall be set to the default values
147
3GPP2 C.P0087-0 v0.83
5.6.5.1 Procedures
This protocol uses the Generic Configuration Protocol (see section 14.7 in [1]) to define the
processing of the configuration messages.
3
4
section, in the order specified, when directed by the InUse instance of the Session
6
7
9
10
11
instance of the protocol shall be added to the public data of the InUse instance of the
protocol.
13
If the InUse instance of this protocol has the same subtype as this instance of the protocol,
then
14
the protocol.
12
15
16
17
18
20
If the InUse instance of this protocol does not have the same subtype as this instance of
the protocol, then the access terminal and the access network shall perform the following:
21
19
22
23
24
The InConfiguration instance of the protocol shall become the InUse instance of the
protocol for the Signaling Adaptation Protocol.
InUse protocol.
25
26
27
28
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
MessageID
29
Attribute dependent

148
3GPP2 C.P0087-0 v0.83
TransactionID
1
2
AttributeRecord
The
sender
shall
increment
this
value
for
each
new
The format of this record is specified in section 14.3 in[1].
Channels
FTC
Addressing
SLP
RTC
Reliable
Priority
unicast
40
6
7
Field
Length (bits)
MessageID
TransactionID

AttributeRecord
Attribute dependent
MessageID
TransactionID
9
10
AttributeRecord
11
12
13
14
15

AttributeRecord is given in section 14.3 in [1]. The sender shall not
16
Channels
Addressing
FTC
RTC
unicast
SLP
Reliable
Priority
17
5.6.6.1 Procedures
18
This protocol does not define any procedures.
19
20
No messages are defined for the InUse instance of this protocol.
21
149
40
3GPP2 C.P0087-0 v0.83
This protocol does not register to receive any indications.
Constant
Meaning
Value
NSAPType
0x1d
NSAPDefault
0x0000
Information record (described in section 14.8 of [1]).
8
9
10
150
3GPP2 C.P0087-0 v0.83
5.7 Default Air-Link Management Protocol
5.7.1 Overview
The Default Air-Link Management Protocol provides the following functions:
General state machine and state-transition rules to be followed by an access terminal and
6an access network for the Connection Layer.
5
Activation and deactivation of Connection Layer protocols applicable to each protocol state.
Mechanism through which access network can redirect access terminal to another network.
The actual behavior and message exchange in each state is mainly governed by protocols that
are activated by the Default Air-Link Management Protocol. These protocols return indications
11which trigger the state transitions of this protocol. These protocols also share data with each
12other in a controlled fashion, by making that data public.
9
10
This protocol can be in one of three states:
13
Initialization State: In this state the access terminal acquires an access network. The
15protocol activates the Initialization State Protocol to execute the procedures relevant to this
16state. The access network maintains a single instance of this state and consequently, executes
17a single instance of the Initialization State Protocol.
14
Idle State: In this state the connection is closed. The protocol activates the Idle State
19Protocol to execute the procedures relevant to this state.
18
Connected State: In this state the connection is open. The protocol activates the Connected
21State Protocol to execute the procedures relevant to this state.
20
Figure 5.7.1 -14 provides an overview of the access terminal states and state transitions. All
transitions are caused by indications returned from protocols activated by the Default Air-Link
24Management Protocol.
22
23
Initial State
NetworkAcquired
Initialization
State
Connected
State
Idle State
NetworkRedirected or
NetworkLost or Supervision Failed
ConnectionClosed or
Supervision Failed
NetworkRedirected
25
26
Figure 5.7.1-14. Default Air Link Management Protocol State Diagram (Access Terminal)
151
3GPP2 C.P0087-0 v0.83
Figure 5.7.1 -15 provides an overview of the access network states and state transitions.
Initial State
IdleState.Connect@@ Opened
Initialization
State
Connect@@ Closed or
Connect@@ Lost
(one for all access terminals)

2
3
Connected
State
Idle State
Figure 5.7.1-15. Default Air Link Management Protocol State Diagram (Access Network)
Table 5.7.1 -27 provides a summary of the Connection Layer and MAC Layer protocols that are
5active in each state.
4
Table 5.7.1-27. Active Protocols Per Air Link Management Protocol State
Idle State
Connected State
Idle State Protocol
Control Channel MAC

Protocol 62
Control Channel MAC Protocol
Control Channel MAC

Protocol

Protocol

Protocol 63

Protocol

Protocol 64
7
Table 5.7.1-2 provides a summary of the Connection Layer protocol that are active in each
state when access terminal TunnelModeEnabled is equal to 1.
8
9
62 Activated by the Initialization State Protocol
63 Only during connection setup
152
3GPP2 C.P0087-0 v0.83
1
2
terminal TunnelModeEnabled is equal to 1
Idle State
Idle State Protocol

Table 5.7.1-3 provides a summary of the Connection Layer protocol that are active in each
state when access terminal TunnelModeEnabled is equal to 0.
3
4
5
6
terminal TunnelModeEnabled is equal to 0
Idle State
Connected State
Idle State Protocol
Control Channel MAC

Protocol 65
Signaling Adaptation
Protocol
Control Channel MAC Protocol
Control Channel MAC

Protocol

Protocol

Protocol 66

Protocol

Protocol 67

7
8
5.7.2 OpenConnection
10
65 Activated by the Initialization State Protocol
153
3GPP2 C.P0087-0 v0.83
If the protocol receives the OpenConnection command in the Initialization State it shall
1
If the protocol subtype of the Signaling Adaptation protocol is equal to 0x0000 or if there is
no InUse instance of the Signaling Adaptation Protocol, then the access terminal shall
5
queue the command and execute it when the access terminal enters the Idle State.
3
4
If the protocol subtype of the Signaling Adaptation protocol is not equal to 0x0000 and
TunnelModeEnabled, provided as public data of the Signaling Adaptation protocol, is not
8
equal to 1, then the access terminal shall queue the command and execute it when the
9
access terminal enters the Idle State.
6
7
If the protocol subtype of the Signaling Adaptation protocol is not equal to 0x0000 and
11
TunnelModeEnabled, provided as public data of the Signaling Adaptation protocol, is equal
12
to 1, then the access terminal shall issue a SignalingAdaptation.OpenConnection
13
command.
10
The access network shall ignore the command in the Initialization State.
14
If the protocol receives this command in the Idle State and if the protocol subtype of the
Signaling Adaptation protocol is equal to 0x0000 or if there is no InUse instance of the
17Signaling Adaptation Protocol, then:
15
16
Access terminal shall issue an IdleState.OpenConnection command.
18
Access network shall issue an IdleState.OpenConnection command.
19
If the protocol receives this command in the Idle State and if the protocol subtype of the
Signaling Adaptation protocol is not equal to 0x0000, then the protocol shall perform the
22following:
20
21
If TunnelModeEnabled, provided as public data of the Signaling Adaptation protocol, is

equal to 1, it shall issue a SignalingAdaptation.OpenConnection command.
23
24
Otherwise, it shall issue an IdleState.OpenConnection command.
25
If the protocol receives this command in the Connected State the command shall be ignored.
26
5.7.3 CloseConnection
27
28
If the protocol receives the CloseConnection command in the Connected State:
29
Access terminal shall issue a ConnectedState.CloseConnection command.
30
Access network shall issue a ConnectedState.CloseConnection command.
31
If the protocol receives this command in any other state and if the protocol subtype of the
Signaling Adaptation protocol is equal to 0x0000, then it shall be ignored.
32
33
If the protocol receives this command in the Initialization or Idle State and if the protocol
35subtype of the Signaling Adaptation protocol is not equal to 0x0000:
34
154
3GPP2 C.P0087-0 v0.83
If TunnelModeEnabled, provided as public data of the Signaling Adaptation protocol, is

2
equal to 1, then the access terminal shall issue a SignalingAdapation.CloseConnection
3
command.
1
Otherwise, it shall be ignored.
5.7.4 General Requirements for the Access Terminal in Idle State
The access terminal shall issue the following commands upon entering this state:
IdleState.Activate
RouteUpdate.Activate
8
9
If the access terminal had a queued OpenConnection command, it shall issue an

IdleState.OpenConnection command.
10
11
If the protocol receives an IdleState.ConnectionOpened indication the access terminal shall:
12
13
If the protocol subtype of the Signaling Adaptation protocol is equal to 0x0000 or

TunnelModeEnabled, provided as public data of the Signaling Adaptation protocol, is
equal to 0, the access terminal shall perform the cleanup procedures defined in
8.2.6.1.3.1.2 of [1] and transition to the Connected State.
Otherwise the access terminal shall ignore this indication.
14
15
16
17
If
the
protocol
receives
an
IdleState.ConnectionFailed,
ForwardTrafficChannelMAC.SupervisionFailed,
or
20ReverseTrafficChannelMAC.SupervisionFailed indication, the access terminal shall:
18
19
Issue an IdleState.Close command,
Issue a RouteUpdate.Close command,
21
22
a
a
If the protocol
receives a Redirect message, a RouteUpdate.NetworkLost, an
OverheadMessages.SupervisionFailed,
an
OverheadMessages.ANRedirected,
a
25ControlChannelMAC.SupervisionFailed, or an AccessChannelMAC.SupervisionFailed indication,
26the access terminal shall:
23
24
Issue a RouteUpdate.Deactivate command,
Issue an OverheadMessages.Deactivate command,
Issue a ControlChannelMAC.Deactivate command,
Perform the cleanup procedures defined in 8.2.6.1.3.1.2 of [1], and
Transition to the Initialization State.
27
28
29
30
31
5.7.5 General Requirements for the Access Network in Idle State
32
33
The access network shall issue the following commands upon entering this state:
34
35
IdleState.Activate
155
3GPP2 C.P0087-0 v0.83
If
the
protocol
receives
an
indication,
3ReverseTrafficChannelMAC.SupervisionFailed indication, the access network shall:
2
Issue an IdleState.Close command,
Issue a RouteUpdate.Close command.
4
5
or
If the protocol receives an IdleState.ConnectionOpened indication the access terminal shall:
6
7
If the protocol subtype of the Signaling Adaptation protocol is equal to 0x0000 or

TunnelModeEnabled, provided as public data of the Signaling Adaptation protocol, is
equal to 0, the access network shall perform the cleanup procedures defined in
8.2.6.1.3.2.2 of [1] and transition to the Connected State.
Otherwise the access network shall ignore this indication.
8
9
10
11
The access network may send the access terminal a Redirect message to redirect it from the
13current serving network and optionally, provide it with information directing it to another
14network. If the access network sends a Redirect message it shall
12
Issue a RouteUpdate.Deactivate command,
Perform the cleanup procedures defined in 8.2.6.1.3.2.2 of [1].
15
16
5.7.6 Commands Sent
17
18
19
InitializationState.Activate
20
InitializationState.Deactivate
21
IdleState.Activate
22
IdleState.Deactivate
23
IdleState.Close
24
IdleState.OpenConnection
25
ConnectedState.Activate
26
ConnectedState.Deactivate
27
ConnectedState.CloseConnection
28
29
RouteUpdate.Deactivate
30
RouteUpdate.Close
31
32
33
SignalingAdaptation.OpenConnection
34
156
3GPP2 C.P0087-0 v0.83
1
2
157
3GPP2 C.P0087-0 v0.83
5.8 Default Connected State Protocol
This section describes the procedures for the Inactive State referred in section 8.6.6.1 of [1].
If the access terminal receives a SignalingAdaptation.ConnectionClosed indication in this state,

then the access terminal shall return a ConnectionClosed indication.
4
5
5.8.2 Indications
8
9
10
158
3GPP2 C.P0087-0 v0.83
5.9 Default Packet Consolidation Protocol
This section supersedes 8.8.3 of [1].
The Protocol Data Unit for this protocol is a Connection Layer packet. Connection Layer packets
5contain Session Layer packets destined to or from the same access terminal address.
4
Two types of Connection Layer packets are defined:
7
8
9
10
11
12
13
Format A: These packets are maximum length packets (including lower layer headers).
Format A packets contain one Session Layer packet and do not have Connection Layer
headers or padding.
Format B: These packets are maximum length packets (including lower layer headers).
Format B packets contain one or more Session Layer packets and have a Connection Layer
header(s). The protocol places the Connection Layer header defined in 8.8.6.3.2 of [1] in
front of each Session Layer packet and enough padding to create a maximum length packet.
Format A provides an extra octet of payload per packet.
14
The packet format type is passed with the packet to the lower layers.
15
The Connection Layer encapsulation is shown in Figure 5.9.1-1 and Figure 5.9.1-2.
16
If the protocol subtype of the InUse instance of the Signaling Adaptation protocol is equal to
180x0000 or if there is no InUse instance of the Signaling Adaptation Protocol, Aall transmitted
19packets are forwarded to the Security Layer. Otherwise, all transmitted packets are forwarded to
20the Signaling Adaptation protocol.
17
All received packets are forwarded to the Session Layer after removing the Connection Layer
headers.
21
22
The maximum size Session Layer packet the protocol can encapsulate depends on the Physical
24Layer channel on which this packet will be transmitted and on the specific security protocols
25negotiated.
23
Connection Layer packet

Session
Layer
packet
26
27
Figure 5.9.1-1. Connection Layer Packet Structure (Format A)
159
3GPP2 C.P0087-0 v0.83
Connection Layer packet

Connection
Layer
header
Session
Layer
packet
Connection
Layer
header
Session
Layer
packet
Padding
1
2
Figure 5.9.1-2. Connection Layer Packet Structure (Format B)
5.9.2 Access Terminal Requirement of Format A Packets
The access terminal shall create a Format A Connection Layer packet, only if the highest
priority pending Session Layer packet will fill the lowerSecurity Llayer payload.
5
6
80x0000 or if there is no InUse instance of the Signaling Adaptation Protocol , tThe access
9terminal shall forward the Connection Layer packet for transmission to the Security Layer.
10Otherwise, the access terminal shall forward the Connection Layer packet for transmission to
7
5.9.3 Access Terminal Requirement of Format B Packets
12
13
The access terminal shall create a Format B Connection Layer packet by adding the
Connection Layer header, defined in 8.8.6.3.2 of [1] in front of every Session Layer packet,
16concatenating the result and adding enough padding to fill the lowerSecurity Llayer payload.
17The resulting packet length shall not exceed the maximum payload that can be carried on the
18Physical Layer Channel, given the transmission rate that will be used to transmit the packet
19and the headers added by the lower layers. All concatenated Connection Layer packets shall be
68
20transmitted on the same Physical Layer Channel .
14
15
The protocol shall use the priority order to determine which Session Layer packets shall be
included in the Connection Layer packet. The protocol shall concatenate and encapsulate
23Session Layer packets into a Connection Layer Packet.
21
22
26terminal shall forward the Connection Layer packet for transmission to the Security Layer.
27Otherwise, the access terminal shall forward the Connection Layer packet for transmission to
24
25
5.9.4 Access Network Requirement of Control Channel Connection Layer Packets
29
This section supercedes 8.8.6.1.5.1.1 of [1].
30
The access network shall not encapsulate Session Layer packets destined to different access
32terminals in the same Connection Layer packet.
31
68 i.e., Access Channel or Reverse Traffic Channel.
160
3GPP2 C.P0087-0 v0.83
The access network may encapsulate multiple Session Layer packets destined to a single
2access terminal in the same Connection Layer packet.
1
The access network should assign a priority to the Connection Layer packet based on its
component Session Layer packets. If the Connection Layer packet contains a single Session
5Layer packet, the priority of the Connection Layer packet should be the priority received with
6the Session Layer packet.
3
4
If any Session Layer packet encapsulated in a Connection Layer packet is marked for
8transmission in a synchronous capsule, the Connection Layer packet shall be marked for
9transmission in a synchronous capsule. Connection Layer packets may be either Format A or
10Format B. When the access network forms a Format A Connection Layer packet, it shall set the
11Format A Connection Layer packet to the Session Layer packet. The resulting packet length
12shall not exceed the maximum payload that can be carried in a Control Channel MAC Layer
13packet given the headers added by the lower layers. When the access network forms a Format B
14Connection Layer packet, it shall create the Format B Connection Layer packet by appending
15the Connection Layer header defined in 8.8.6.3.2 of [1] in front of every Session Layer packet it
16is encapsulating in this Connection Layer packet and then concatenating the result. The
17resulting packet length shall not exceed the maximum payload that can be carried in a Control
18Channel MAC Layer packet given the headers added by the lower layers.
7
0x0000 or if there is no InUse instance of the Signaling Adaptation Protocol , Tthe access
21network shall forward the Connection Layer packet for transmission to the Security Layer.
22Otherwise, the access network shall forward the Connection Layer packet for transmission to
19
20
5.9.5 Access Network Requirement of Format A Packets of Forward Traffic Channel
24
25
The access network shall create a Format A Connection Layer packet, only if the length of the
27highest priority pending Session Layer packet will fill the lowersecurity layer payload.
26
28
29
5.9.6 Access Network Requirement of Format B Packets of Forward Traffic Channel
33
34
The access network shall create a Format B Connection Layer packet by adding the Connection
36Layer header defined in 8.8.6.3.2 of [1] in front of every Session Layer packet, concatenating
37the result and adding padding to fill the lowerSecurity Llayer payload. The resulting packet
38length shall not exceed the maximum payload that can be carried on the Forward Traffic
39Channel given the headers added by the lower layers.
35
The protocol shall encapsulate and concatenate Session Layer packets in priority order.
40
161
3GPP2 C.P0087-0 v0.83
20x0000 or if there is no InUse instance of the Signaling Adaptation Protocol, the The access
1
162
6 INITIAL MEAN OUTPUT POWER REQUIREMENT FOR ACTIVE INTER-RAT HANDOFF
6.1 Access Terminal Subtype 3 RTCMAC Protocol Requirement
This section provides the initial mean output power calculation requirement for an access
5terminal when it performs the inter-RAT active handoff. The access teminalterminal shall
6follow the subtype 3 Reverse Traffic Channel MAC protocol procedures as defined in [1] and the
7inter-RAT interworking requirement specified in this section.
4
6.1.1 Return Indications
This section supersedes to section 10.11.2.2 of [1].
10
LinkAcquired
11
SupervisionFailed
12
OpenLoopParametersIssued
13
6.1.2 Public Data
14
15
16
17
18
ARQMode
19
AuxiliaryPilotChannelGain
20
AuxiliaryPilotChannelMinPayload
21
Rate1M8Supported
22
RRI (Payload Index and sub-packet Index)
23
RRIChannelGain
24
TxT2P
25
RPCStep
26
MIRTCMAC
27
MQRTCMAC
28
RAChannelGain for each pilot in the Active Set
29
X0
30
31
3GPP2 C.P0087-0 v0.83
When the protocol is in the Inactive State the access terminal and the access network wait for
2an Activate command.
1
Upon entering the state, the access terminal shall set X0 public data to NULL.
Upon entering the state, and if the access terminal has queued HRPDOpenLoopParameters
message, the access terminal shall discard the queued HRPDOpenLoopParameters message.
4
5
If the access terminal receives an HRPDOpenLoopParameters message in this state, then the
7access terminal shall queue the latest HRPDOpenLoopParameters message for processing in
8the Setup State.
6
If the access terminal or the access network receives a SignalingAdaptation.LinkAcquired

10indication in this state, then the protocol shall return a LinkAcquired indication.
9
When the access network sends a HRPDOpenLoopParameters message it shall return a

OpenLoopParametersIssued indication.
11
12
6.1.4 Setup State
13
This section refers to section 10.11.6.1.5 of [1].
14
6.1.4.1 Access Terminal Requirements For Calculating Initial Mean Output Power
15
This section is under the Access Terminal Requirements section referring to 10.11.6.1.5.1 of
17[1].
16
Upon
entering
the
Setup
State,
if
the
access
terminal
has
queued
an
HRPDOpenLoopParameters message, the access terminal shall calculate the initial mean
20output power, X0, of the Pilot Channel of the Reverse Traffic Channel as follows:
18
19
X0 = - Mean RX Power (dBm) + OpenLoopAdjust + PilotInitialAdjust
21
where
22
PilotInitialAdjust = InitialAdjust + min(PilotStrengthCorrectionMax, max(PilotStrengthNominal

PilotStrength, PilotStrengthCorrectionMin)),
23
24
PilotStrength is the pilot strength of the sector to which the access terminal is initiating the
26Reverse Traffic Channel transmission and the Mean R X Power is estimated throughout the
27initial
Pilot
Channel
transmission.
If
the
open
loop
parameters
in
the
28HRPDOpenLoopParameters
message are indicated common for all the pilots in the
message,
the
parameters
PilotStrengthNominal,
30PilotStrengthCorrectionMin, PilotStrengthCorrectionMax, InitialAdjust and OpenLoopAdjust
69
31are set to values common to all the PilotPNs in the received TrafficChannelAssignment
32message. If the open loop parameters in the HRPDOpenLoopParameters message are grouped
33at a per pilot basis, the parameters in the above equation shall be corresponding to the forward
34link pilot in the TrafficChannelAssignment message selected by the access terminal.
The
35strength of this pilot shall be used by the access terminal as the PilotStrength in above
36equation.
25
69 TrafficChannelAssignment message is sent right after the HRPDOpenLoopParameters message is
4sent.
3GPP2 C.P0087-0 v0.83
6.1.5 Message Format
This section refers to section 10.11.6.2 of [1].
6.1.5.1 HRPDOpenLoopParameters
The access network shall send an HRPDOpenLoopParameters message as part of the

preparation for an active handoff from the other radio access technology to HRPD.
4
5
6
Field
MessageID
9
10
11
12
NumPilots
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
PilotPN
31
32
33
34
OpenLoopAdjust
35
36
37
38
Length (bits)
Message ID
NumPilots
If NumPilots is set to 0000, one

occurrence of the following record; If
NumPilots is not set to 0000, NumPilots
occurrences of the following record:
The
access
network
shall
set this field to
0x07.
The
access
network
shall
8
OpenLoopAdjust
set this field to
either a zero or
5
InitialAdjust
a
non-zero
1
PilotStrengthIncluded
value. If this
field is set to
3
PilotStrengthNominal
zero, it indicates
3
PilotStrengthCorrectionMin
that the values
in the following
3
PilotStrengthCorrectionMax
fields
of
the
occurrence are
Variable
Reserved
common to all
the PilotPNs in
the TrafficChannelAssignment message. Otherwise, the same value as
the NumPilots field of the appended TrafficChannelAssignment message
shall be set to the field, and the following fields are associated with the
PilotPN in the occurance.
0 or 9
PilotPN
If NumPilots field is not set to zero, the access network shall set this field
to
same
value
as
the
PilotPN
field
of
the
appended
TrafficChannelAssignment message. Otherwise, this field shall be
omitted.
The access network shall set this field to the negative of the nominal
power to be used by access terminals in the open loop power estimate,
expressed as an unsigned value in units of 1 dB. The value used by the
access terminal is -1 times the value of this field.
3GPP2 C.P0087-0 v0.83
InitialAdjust
The access network shall set this field to the correction factor to be used
by access terminals in the open loop power estimate for the initial
transmission on the Reverse Traffic Channel, expressed as a twos
complement value in units of 1 dB.
1
2
3
4
PilotStrengthIncluded
The access network shall set this field to 0 if the PilotStrengthNominal,

PilotStrengthCorrectionMin and PilotStrengthCorrectionMax fields are
omitted in the AccessParameter message. Otherwise it shall set this field
to 1.
6
7
8
9
PilotStrengthNominal
10
13
If the PilotStrengthIncluded field is set to 0 the access network shall set

this value to 000. Otherwise, the access network shall set this field
according to Table 6.1.5 -28.
14
Table 6.1.5-28PilotStrengthNominal Encoding
11
12
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
15
PilotStrengthCorrectionMin
17
18
this value to 000. Otherwise, the access network shall set this field
19
according to Table 6.1.5 -29.
16
20
Table 6.1.5-29PilotStrengthCorrectionMin Encoding
3GPP2 C.P0087-0 v0.83
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
PilotStrengthCorrectionMax
2
3
this value to 000. OtherwieseOtherwise, the access network shall set
4
this field according to Table 6.1.5 -30.
1
Table 6.1.5-30. PilotStrengthCorrectionMax Encoding
Field value
Meaning
(binary)
Reserved
000
0 dB
001
1 dB
010
2 dB
011
3 dB
100
4 dB
101
5 dB
110
Reserved
111
Reserved
The access network shall set this field to zero, The access terminal shall
set ignore this field.
6
7
8
Channels
Addressing
SLP
CC
unicast
6.2 Estimated Open-Loop Output Power
10
11
Priority
Best Effort
40
3GPP2 C.P0087-0 v0.83
Open-loop operation shall be based on the power of the received Forward Pilot Channel (see
213.3.1.3.2.1 of [1]).
1
The nominal access probe structure and its transmit power requirements are defined as part of
the Access Channel MAC Protocol. The power of the Access Data Channel relative to that of the
5Pilot Channel shall be as specified in Table 6.2-31 in which DataOffsetNom, DataOffset9k6,
6DataOffset19k2, and DataOffset38k4 are public data of the Access Channel MAC Protocol. The
7output power of the Pilot Channel during the preamble portion of an access probe shall be
8increased relative to the nominal Pilot Channel power during the data portion of the probe by
9an amount such that the total output power of the preamble and data portion of the access
10probe, if transmitted at 9.6 kbps, are the same.
3
4
Once instructed by the Reverse Traffic Channel MAC Protocol, the access terminal initiates
12Reverse Traffic Channel transmission.
11
If the initial mean output power of the Pilot Channel of the Reverse Traffic Channel is
calculated by the Reverse Traffic Channel MAC Protocol (see 6.1), then
13
14
15
16
17
18
19
20
21
The initial mean output power of the Pilot Channel of the Reverse Traffic Channel shall be
set to X0, which is public data of the Reverse Traffic Channel MAC Protocol.
The subsequent mean output power of the Pilot Channel of the total reverse link
transmission shall be the mean output power of the Pilot Channel at the initial Reverse
Traffic Channel transmission minus the difference in the forward link mean received signal
power from the initial Pilot Channel transmission to the current Reverse Traffic Channel
transmission, plus closed loop corrections as specified in 13.2.1.2.4.2 of [1].
Otherwise,
22
23
24
25
26
27
28
29
30
31
The initial mean output power of the Pilot Channel of the Reverse Traffic Channel shall be
equal to the mean output power of the Pilot Channel at the end of the last Access Channel
probe minus the difference in the forward link mean received signal power from the end of
the last Access Channel probe to the start of the Reverse Traffic Channel transmission.
The subsequent mean output power of the Pilot Channel of the total reverse link
transmission shall be the mean output power of the Pilot Channel at the end of the last
Access Channel probe minus the difference in the forward link mean received signal power
from the end of the last Access Channel probe to the current Reverse Traffic Channel
transmission, plus closed loop corrections as specified in13.2.1.2.4.2 of [1].
The accuracy of the incremental adjustment to the mean output power, as dictated by the
33Access Channel MAC Protocol and the Reverse Traffic Channel MAC Protocol, shall be 0.5 dB
34or 20% of the change in dB, whichever is greater.
32
When the access terminal is transmitting the Access Channel, the power of the Data Channel
36relative to that of the Pilot Channel during the data portion of the Access Channel
37transmission shall be as specified in Table 6.2-31 in which DataOffsetNom, DataOffset9k6,
38DataOffset19k2, and DataOffset38k4 are public data of the Access
Channel MAC Protocol.
39When the access terminal is transmitting the Access Channel, the power of the Pilot Channel
40during the preamble portion of the Access Channel transmission shall be equal to the total
41power transmitted during the data portion of the Access Channel transmission when the Data
42Channel is transmitted at 9.6 kbps.
35
3GPP2 C.P0087-0 v0.83
Table 6.2-31. Relative Power Levels vs. Data Rate for Access Channel Transmissions
Data Rate
(kbps)
Data Channel Gain Relative to Pilot

(dB)
(Data Channel Is Not Transmitted)
9.6
DataOffsetNom + DataOffset9k6 + 3.75
19.2
38.4
During the transmission of the RRI Channel, the power of the RRI Channel relative to that of
4the Pilot Channel shall be as specified by RRIChannelGain, where RRIChannelGain is public
5data of the Reverse Traffic Channel MAC Protocol.
3
During the transmission of the DSC Channel, the power of the DSC Channel relative to that of
7the Pilot Channel shall be as specified by DSCChannelGain, where DSCChannelGain is public
8data of the Forward Traffic Channel MAC Protocol.
6
During the transmission of the DRC Channel, the power of the DRC Channel relative to that of
10the Pilot Channel shall be as specified by DRCChannelGain, where DRCChannelGain is public
11data of the Forward Traffic Channel MAC Protocol.
9
During the transmission of the ACK Channel, the power of the ACK Channel relative to that of
13the Pilot Channel shall be as specified by ACKChannelGain, where ACKChannelGain is public
14data of the Forward Traffic Channel MAC Protocol if the access terminal is transmitting an ACK
15in response to a Single User packet.
12
During the transmission of the ACK Channel, the power of the ACK Channel relative to that of
the Pilot Channel shall be as specified by ACKChannelGain + DeltaACKChannelGainMUP if the
18access terminal is transmitting an ACK in response to a Multi-User packet, where
19ACKChannelGain and DeltaACKChannelGainMUP are public data of the Forward Traffic
20Channel MAC Protocol.
16
17
During the transmission of the Data Channel, the power of the Data Channel relative to that of
the Pilot Channel shall be as specified by TxT2P, where TxT2P is public data of the Reverse
23Traffic Channel MAC Protocol.
21
22
The Auxiliary Pilot Channel shall be transmitted during the n th half slot if the Reverse Traffic
25Channel transmit payload is greater than or equal to AuxiliaryPilotChannelMinPayload during
26half slots n1 or n+1, where AuxiliaryPilotChannelMinPayload is public data of the Reverse
24
If the Auxiliary Pilot Channel is transmitted during the n th half slot, its power shall be
29specified relative to the maximum of the Data Channel Gains during half-slots n1 and n+1
30by AuxiliaryPilotChannelGain, where AuxiliaryPilotChannelGain is public data of the Reverse
28
3GPP2 C.P0087-0 v0.83
The access terminal shall maintain the power of the RRI Channel, DSC Channel, DRC
2Channel, ACK Channel, and Data Channel relative to that of the Pilot Channel, to within 0.25
3dB of the specified values.
1
The access terminal shall maintain the power of the Auxiliary Pilot Channel during the n th
5half slot relative to that of the maximum of the Data Channel Gains during half slots n 1 and
6n+1 to within 0.25 dB of the specified values.
4
If TxT2P is less than or equal to TxT2P min (both public data of the Reverse Traffic Channel
8MAC Protocol) and the access terminal is unable to transmit the Reverse Traffic Channel at the
9required output power level, the access terminal shall reduce the power of the DRC Channel
10and the ACK Channel accordingly. The maximum power reduction for the DRC Channel
11corresponds to gating off the DRC Channel. The maximum power reduction for the ACK
12Channel corresponds to gating off the ACK Channel. If the ACK Channel is active, the ACK
13Channel power reduction shall occur only after the DRC Channel has been gated off. The
14access terminal shall perform the power reduction within one slot of determining that the
15access terminal is unable to transmit at the requested output power level.
7
16
17
18
19
20
3GPP2 C.P0087-0 v0.83
No text.
ANNEX A E-UTRAN-HRPD CALL FLOW EXAMPLES
This is an informative annex which contains examples of call flow.
3
4
Figure A-16 Access Terminal, UATI Assignment and Session Configuration over E-UTRAN
1
2
Figure A-17 Access Network, UATI Assignment and Session Configuration over E-UTRAN
1
2
Figure A-18 Access Terminal, E-UTRAN to HRPD Idle Handoff
1
2
Figure A-19 Access Network, E-UTRAN to HRPD Idle Handoff
1
2
Figure A-20 Access Terminal, E-UTRAN to HRPD Active Handoff
1
2
Figure A-21 Access Network, E-UTRAN to HRPD Active Handoff

C.P0087-0 E-UTRAN-HRPD Connectivity and Interworking - Air Interface Aspects v0.83 02apr2009 (Draft)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

C.P0087-0 E-UTRAN-HRPD Connectivity and Interworking - Air Interface Aspects v0.83 02apr2009 (Draft)

Uploaded by

Copyright:

Available Formats

1

3GPP2 C.P0087-0 v0.83

Change table of content

All SWG22 approved contributions located under

Clean up reference and section numbers

3GPP2 C.P0087-0 v0.83

3GPP2 C.P0087-0 v0.83

1.1 Introduction .........................................................................................................

1.2 Scope of This Document .......................................................................................

1.3 Requirement Language.........................................................................................

1.4 Architecture Reference Model................................................................................

1.5 Protocol Overview..................................................................................................

2 Access terminal specific procedures............................................................................2-1

2.1 Access Terminal Bootup Procedure.......................................................................

2.2 E-UTRAN to HRPD Idle Handoff Procedure............................................................

2.3 Enhanced Multi-flow Packet Application Negotiation .............................................

2.4 Session Management Protocol Activation ..............................................................

3.1 Additional Requirement to support eHRPD operation ..........................................

4.1 Default Session Management Protocol ...................................................................

4.1.1 Keep Alive Functions .......................................................................................

4.2 Default Address Management Protocol................................................................

4.2.2 Primitives and Public Data............................................................................

4.2.2.2 Return Indications...................................................................................

4.2.2.3 Public Data.............................................................................................

4.2.4 Setup State...................................................................................................

4.2.4.1 Access Terminal Requirements................................................................

3GPP2 C.P0087-0 v0.83

4.2.4.2 Access Network Requirements.................................................................

4.2.5 Open State....................................................................................................

4.2.5.1 Access Terminal Requirements................................................................

4.2.5.2 Access Network Requirements.................................................................

4.2.6 Message Formats..........................................................................................

4.2.6.2 InterRATMobilityIndication ......................................................................

4.2.8 Configuration Attributes...............................................................................

4.2.9 Protocol Numeric Constants..........................................................................

5.1 Inter-RAT Signaling Adaptation Protocol ................................................................

5.1.2 Primitives and Public Data..............................................................................

5.1.2.2 Return Indications....................................................................................

5.1.2.3 Public Data...............................................................................................

5.1.3 Protocol Data Unit...........................................................................................

5.1.4 Protocol Initialization......................................................................................

5.1.4.1 Protocol Initialization for the InConfiguration Protocol Instance .................

5.1.4.2 Protocol Initialization for the InUse Protocol Instance ................................

5.1.5.2 Commit Procedures...................................................................................

5.1.5.3 Message Formats.......................................................................................

5.1.5.3.2 ConfigurationResponse ........................................................................

5.1.6.1.1 Command Processing..........................................................................

5.1.6.1.1.1 OpenConnection ............................................................................

3GPP2 C.P0087-0 v0.83

5.1.6.1.1.2 CloseConnection ............................................................................

5.1.6.1.2 Close State..........................................................................................

5.1.6.1.2.1 Access Terminal Requirements.......................................................

5.1.6.1.2.2 Access Network Requirements........................................................

5.1.6.1.3 Setup State..........................................................................................

5.1.6.1.3.1 Access Terminal Requirements.......................................................

5.1.6.1.3.2 Access Network Requirements......................................................

5.1.6.1.4 Open State.........................................................................................

5.1.6.1.5 Processing the

5.1.6.2 Message Formats.....................................................................................

5.1.6.3 Header Format........................................................................................

5.1.6.4 Interface to Other Protocols.....................................................................

5.1.6.4.1 Commands Sent................................................................................

5.1.7 Configuration Attributes...............................................................................

5.1.8 Protocol Numeric Constants..........................................................................