Read A.S0007-A v3.0 HRPD IOS pub.doc text version

3GPP2 A.S0007-A v3.0 Date: May 2007

1

2

3

Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Packet Control Function

4

COPYRIGHT © 2007, 3GPP2

3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at [email protected] Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

A.S0007-A v3.0 HRPD IOS

Table of Contents

Foreword ....................................................................................................................................................viii 1 1.1 1.2 1.3 1.3.1 1.3.2 1.3.3 1.4 1.4.1 1.4.2 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 2 2.1 2.2 2.3 2.3.1 Introduction...................................................................................................................................1-1 Scope.............................................................................................................................................1-1 Document Convention ..................................................................................................................1-1 References.....................................................................................................................................1-1 TIA / EIA ......................................................................................................................................1-1 3GPP2 ...........................................................................................................................................1-2 Other .............................................................................................................................................1-2 Terminology..................................................................................................................................1-3 Acronyms......................................................................................................................................1-3 Definitions ....................................................................................................................................1-3 HRPD IOS Alternative Architecture Reference Model ................................................................1-5 HRPD Micro-Mobility and Macro-Mobility Concepts ................................................................1-6 Compatibility with IS-2001 Standards..........................................................................................1-6 Message Body, Coding, Ordering, and Interpretation of Elements ..............................................1-7 Forward Compatibility Guidelines ...............................................................................................1-8 Message Processing Guidelines ....................................................................................................1-9 Message Definition Guidelines.....................................................................................................1-9 HRPD IOS Assumptions.............................................................................................................1-10 HRPD IOS Interfaces....................................................................................................................2-1 A8-A9 (AN - PCF) Interface ........................................................................................................2-1 A10-A11 (PCF - PDSN) Interface ................................................................................................2-1 A12 (PCF - AN-AAA) Interface and Terminal Authentication....................................................2-1 PPP Session...................................................................................................................................2-2 2.3.1.1 2.3.1.2 2.3.1.3 2.3.2 2.3.3 2.4 2.4.1 2.4.2 Establishment..............................................................................................................2-2 Termination.................................................................................................................2-2 Terminal Authentication .............................................................................................2-2

AN-AAA Support .........................................................................................................................2-2 AN-AAA Requirements................................................................................................................2-3 A13 (PCF - PCF) Interface ...........................................................................................................2-4 A13 Interface Network/Transport Protocol Specification ............................................................2-4 A13 Interface Procedures..............................................................................................................2-5 2.4.2.1 2.4.2.1.1 Session Information Procedure ...................................................................................2-5 A13-Session Information Request..............................................................................2-5

2.4.2.1.1.1 Successful Operation ..................................................................................................2-5 2.4.2.1.1.2 Failure Operation........................................................................................................2-5 i

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

May 2007 A13-Session Information Response ...........................................................................2-5

2.4.2.1.2

2.4.2.1.2.1 Successful Operation ..................................................................................................2-5 2.4.2.1.2.2 Failure Operation........................................................................................................2-5 2.4.2.1.3 A13-Session Information Confirm .............................................................................2-6 2.4.2.1.3.1 Successful Operation ..................................................................................................2-6 2.4.2.1.3.2 Failure Operation........................................................................................................2-6 2.4.2.1.4 A13-Session Information Reject.................................................................................2-6 2.4.2.1.4.1 Successful Operation ..................................................................................................2-6 2.4.2.1.4.2 Failure Operation........................................................................................................2-6 2.5 2.5.1 2.5.2 A14 (AN - PCF) Interface.............................................................................................................2-7 A14 Interface Network/Transport Protocol Specification ............................................................2-7 A14 Interface Procedures..............................................................................................................2-7 2.5.2.1 2.5.2.1.1 UATI Assignment Procedure......................................................................................2-7 A14-UATI Request.....................................................................................................2-7

2.5.2.1.1.1 Successful Operation ..................................................................................................2-7 2.5.2.1.1.2 Failure Operation........................................................................................................2-8 2.5.2.1.2 A14-UATI Assignment ..............................................................................................2-8 2.5.2.1.2.1 Successful Operation ..................................................................................................2-8 2.5.2.1.2.2 Failure Operation........................................................................................................2-8 2.5.2.1.3 A14-UATI Complete ..................................................................................................2-8 2.5.2.1.3.1 Successful Operation ..................................................................................................2-8 2.5.2.1.3.2 Failure Operation........................................................................................................2-8 2.5.2.1.4 A14-UATI Complete Ack ..........................................................................................2-8 2.5.2.1.4.1 Successful Operation ..................................................................................................2-8 2.5.2.1.4.2 Failure Operation........................................................................................................2-8 2.5.2.1.5 A14-UATI Assignment Failure ..................................................................................2-8 2.5.2.1.5.1 Successful Operation ..................................................................................................2-9 2.5.2.1.5.2 Failure Operation........................................................................................................2-9 2.5.2.2 2.5.2.2.1 General Updating Procedure.......................................................................................2-9 A14-General Update...................................................................................................2-9

2.5.2.2.1.1 Successful Operation ..................................................................................................2-9 2.5.2.2.1.2 Failure Operation........................................................................................................2-9 2.5.2.2.2 A14-General Update Complete ..................................................................................2-9 2.5.2.2.2.1 Successful Operation ..................................................................................................2-9 2.5.2.2.2.2 Failure Operation........................................................................................................2-9 2.5.2.3 2.5.2.3.1 Terminal Authentication Procedure ............................................................................2-9 A14-Authentication Command.................................................................................2-10 ii

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

A.S0007-A v3.0 HRPD IOS

2.5.2.3.1.1 Successful Operation ................................................................................................2-10 2.5.2.3.1.2 Failure Operation......................................................................................................2-10 2.5.2.3.2 A14-Authentication Request ....................................................................................2-10 2.5.2.3.2.1 Successful Operation ................................................................................................2-10 2.5.2.3.2.2 Failure Operation......................................................................................................2-10 2.5.2.3.3 A14-Authentication Response ..................................................................................2-10 2.5.2.3.3.1 Successful Operation ................................................................................................2-10 2.5.2.3.3.2 Failure Operation......................................................................................................2-10 2.5.2.3.4 A14-Authentication Completed................................................................................2-11 2.5.2.3.4.1 Successful Operation ................................................................................................2-11 2.5.2.3.4.2 Failure Operation......................................................................................................2-11 2.5.2.3.5 A14-Authentication Completed Ack ........................................................................2-11 2.5.2.3.5.1 Successful Operation ................................................................................................2-11 2.5.2.3.5.2 Failure Operation......................................................................................................2-11 2.5.2.3.6 A14-Authentication Failure ......................................................................................2-11 2.5.2.3.6.1 Successful Operation ................................................................................................2-11 2.5.2.3.6.2 Failure Operation......................................................................................................2-12 2.5.2.3.7 A14-Authentication Failure Ack ..............................................................................2-12 2.5.2.3.7.1 Successful Operation ................................................................................................2-12 2.5.2.3.7.2 Failure Operation......................................................................................................2-12 2.5.2.4 2.5.2.4.1 Session Release.........................................................................................................2-12 A14-Session Release Command...............................................................................2-12

2.5.2.4.1.1 Successful Operation ................................................................................................2-12 2.5.2.4.1.2 Failure Operation......................................................................................................2-12 2.5.2.4.2 A14-Session Release ................................................................................................2-12 2.5.2.4.2.1 Successful Operation ................................................................................................2-12 2.5.2.4.2.2 Failure Operation......................................................................................................2-13 2.5.2.4.3 A14-Session Release Complete................................................................................2-13 2.5.2.4.3.1 Successful Operation ................................................................................................2-13 2.5.2.4.3.2 Failure Operation......................................................................................................2-13 2.5.2.5 2.5.2.5.1 Session Information Transfer Procedure...................................................................2-13 A14-Session Information Update .............................................................................2-13

2.5.2.5.1.1 Successful Operation ................................................................................................2-13 2.5.2.5.1.2 Failure Operation......................................................................................................2-13 2.5.2.5.2 A14-Session Information Update Ack......................................................................2-14 2.5.2.5.2.1 Successful Operation ................................................................................................2-14 2.5.2.5.2.2 Failure Operation......................................................................................................2-14 iii

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

May 2007 Paging Procedure ......................................................................................................2-14 A14-Paging Request .................................................................................................2-14

2.5.2.6 2.5.2.6.1

2.5.2.6.1.1 Successful Operation ................................................................................................2-14 2.5.2.6.1.2 Failure Operation......................................................................................................2-14 2.5.2.6.2 A14-Paging Request Ack .........................................................................................2-15 2.5.2.6.2.1 Successful Operation ................................................................................................2-15 2.5.2.6.2.2 Failure Operation......................................................................................................2-15 2.5.2.6.3 A14-Paging Response...............................................................................................2-15 2.5.2.6.3.1 Successful Operation ................................................................................................2-15 2.5.2.6.3.2 Failure Operation......................................................................................................2-15 2.5.2.6.4 A14-Paging Response Ack .......................................................................................2-15 2.5.2.6.4.1 Successful Operation ................................................................................................2-15 2.5.2.6.4.2 Failure Operation......................................................................................................2-15 2.5.2.7 2.5.2.7.1 Session Keep Alive Procedure..................................................................................2-16 A14-Keep Alive Request..........................................................................................2-16

2.5.2.7.1.1 Successful Operation ................................................................................................2-16 2.5.2.7.1.2 Failure Operation......................................................................................................2-16 2.5.2.7.2 A14-Keep Alive Request Ack ..................................................................................2-16 2.5.2.7.2.1 Successful Operation ................................................................................................2-16 2.5.2.7.2.2 Failure Operation......................................................................................................2-16 2.6 2.6.1 2.6.2 A15 (AN - AN) Interface ............................................................................................................2-17 A15 Interface Network/Transport Protocol Specification ..........................................................2-17 A15 Interface Procedures............................................................................................................2-17 2.6.2.1 2.6.2.1.1 Paging Procedure ......................................................................................................2-17 A15-Paging Request .................................................................................................2-17

2.6.2.1.1.1 Successful Operation ................................................................................................2-17 2.6.2.1.1.2 Failure Operation......................................................................................................2-17 2.6.2.1.2 A15-Paging Response...............................................................................................2-18 2.6.2.1.2.1 Successful Operation ................................................................................................2-18 2.6.2.1.2.2 Failure Operation......................................................................................................2-18 2.6.2.1.3 A15-Paging Response Ack .......................................................................................2-18 2.6.2.1.3.1 Successful Operation ................................................................................................2-18 2.6.2.1.3.2 Failure Operation......................................................................................................2-18 2.7 2.7.1 3 3.1 Ax (AN - PCF) Interface.............................................................................................................2-18 Ax Interface Network/Transport Protocol Specification ............................................................2-18 HRPD IOS Call Flows ..................................................................................................................3-1 AT Originates HRPD Session.......................................................................................................3-1 iv

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

A.S0007-A v3.0 HRPD IOS

3.1.1 3.1.2 3.2 3.2.1 3.2.2 3.2.3 3.3 3.3.1

AT Originates HRPD Session - Successful Terminal Authentication ..........................................3-1 AT Originates HRPD Session - Unsuccessful Terminal Authentication......................................3-5 Re-authentication ..........................................................................................................................3-8 Re-authentication of an AT in Dormant State without Paging Response .....................................3-8 Re-authentication of an AT in Dormant State with Paging Response ........................................3-10 Re-authentication of an AT in Active State ................................................................................3-12 Data Delivery ..............................................................................................................................3-14 Successful Network Initiated Call Re-activation from Dormant State .......................................3-14 3.3.1.1 3.3.1.2 Paging Type 0 (Paging response is not required)......................................................3-14 Paging Type 1 (Paging response is required)............................................................3-16

3.3.2 3.4 3.4.1 3.4.2 3.4.3 3.4.4 3.5 3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.6 3.7 3.7.1 3.7.2 3.8 3.8.1 3.8.2 3.9 3.9.1 3.9.2 4 4.1 4.1.1 4.1.2 4.1.3

AT Initiated Call Re-activation from Dormant State (Existing HRPD Session) ........................3-18 Connection Release.....................................................................................................................3-19 Connection Release on HRPD Network - Initiated by the AT ...................................................3-19 Connection Release on HRPD Network - Initiated by the AN...................................................3-19 Connection Release on HRPD Network - Initiated by the PCF..................................................3-20 Connection Release Caused by Air Link Lost ............................................................................3-20 HRPD Session Release ...............................................................................................................3-22 HRPD Session Release - Initiated by the AT (A8 Connection Exists).......................................3-22 HRPD Session Release - Initiated by the AT (A8 Connection does not Exist) ..........................3-23 HRPD Session Release - Initiated by the AN (A8 Connection Exists) ......................................3-24 HRPD Session Release - Initiated by the PCF (A8 Connection Exists) .....................................3-25 HRPD Session Release - Initiated by the PCF (A8 Connection does not Exist) ........................3-26 Packet Data Session Release - Initiated by the PDSN ................................................................3-27 Dormant Handoff of HRPD AT between PCFs - Served by the Same PDSN............................3-28 PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information.............3-28 Dormant PCF-PCF Handoff with HRPD Session Information Transfer Failure........................3-30 Active HRPD Session .................................................................................................................3-31 Deactivation/Activation of Data Flow During an Active HRPD Session...................................3-31 Session Information Update During an Active HRPD Session ..................................................3-32 Mobility Management.................................................................................................................3-33 Route Updating of a dormant AT ...............................................................................................3-33 Session Keep Alive Procedure of a dormant AT ­ Initiated by the PCF ....................................3-34 HRPD and 1x IOS Transition Call Flows.....................................................................................4-1 Dormant Cross System Handoff - MS/AT Served by the Same PDSN........................................4-1 1x to HRPD Dormant Packet Data Session Handoff - Existing HRPD Session...........................4-1 1x to HRPD Dormant Packet Data Session Handoff - New HRPD Session ................................4-3 HRPD to 1x Dormant Packet Data Session Handoff....................................................................4-7 v

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

May 2007

4.2 4.2.1 4.2.2 4.2.3 4.3 4.4 5 5.1 5.1.1

MS/AT Terminated Voice Call During Active HRPD Packet Data Session................................4-9 MS/AT Terminated Voice Call During Active HRPD Data Packet (Intra-PDSN/Inter-PCF) .....4-9 AT Leaving During an Active HRPD Data Session ...................................................................4-11 MS/AT Terminated Voice Call During Active HRPD Packet Data Session (Intra-PCF) ..........4-12 1x to HRPD Active Packet Data Session Transition ..................................................................4-14 Status Management Supported by Feature Invocation................................................................4-15 Messages, Information Elements and Timer Definitions..............................................................5-1 Message Definitions......................................................................................................................5-1 A13 Message Definitions..............................................................................................................5-1 5.1.1.1 5.1.1.2 5.1.1.3 5.1.1.4 A13-Session Information Request ..............................................................................5-1 A13-Session Information Response............................................................................5-2 A13-Session Information Confirm..............................................................................5-3 A13-Session Information Reject.................................................................................5-3 A14-UATI Request.....................................................................................................5-5 A14-UATI Assignment...............................................................................................5-6 A14-UATI Complete ..................................................................................................5-9 A14-UATI Complete Ack.........................................................................................5-10 A14-UATI Assignment Failure ................................................................................5-11 A14-General Update .................................................................................................5-12 A14-General Update Complete.................................................................................5-14 A14-Authentication Command .................................................................................5-15 A14-Authentication Request.....................................................................................5-16 A14-Authentication Response ..................................................................................5-17 A14-Authentication Completed ................................................................................5-18 A14-Authentication Completed Ack ........................................................................5-19 A14-Authentication Failure ......................................................................................5-20 A14-Authentication Failure Ack...............................................................................5-21 A14-Session Release Command ...............................................................................5-21 A14-Session Release.................................................................................................5-23 A14-Session Release Complete ................................................................................5-25 A14-Session Information Update..............................................................................5-26 A14-Session Information Update Ack ......................................................................5-27 A14-Paging Request .................................................................................................5-27 A14-Paging Request Ack..........................................................................................5-29 A14-Paging Response ...............................................................................................5-30 A14-Paging Response Ack .......................................................................................5-31 vi

5.1.2

A14 Message Definitions..............................................................................................................5-5 5.1.2.1 5.1.2.2 5.1.2.3 5.1.2.4 5.1.2.5 5.1.2.6 5.1.2.7 5.1.2.8 5.1.2.9 5.1.2.10 5.1.2.11 5.1.2.12 5.1.2.13 5.1.2.14 5.1.2.15 5.1.2.16 5.1.2.17 5.1.2.18 5.1.2.19 5.1.2.20 5.1.2.21 5.1.2.22 5.1.2.23

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

A.S0007-A v3.0 HRPD IOS A14-Keep Alive Request ..........................................................................................5-32 A14-Keep Alive Request Ack...................................................................................5-33 A15-Paging Request .................................................................................................5-34 A15-Paging Response ...............................................................................................5-35 A15-Paging Response Ack .......................................................................................5-36

5.1.2.24 5.1.2.25 5.1.3 5.1.3.1 5.1.3.2 5.1.3.3 5.2 5.2.1

A15 Message Definitions............................................................................................................5-34

Information Element Definitions ................................................................................................5-38 A13 Information Element Definitions ........................................................................................5-38 5.2.1.1 5.2.1.2 5.2.1.3 5.2.1.4 5.2.1.5 5.2.1.6 5.2.1.7 5.2.1.8 5.2.1.9 5.2.1.10 Information Element Identifiers................................................................................5-38 A13 Message Type ...................................................................................................5-38 Unicast Access Terminal Identifier (UATI 128). .....................................................5-38 Security Layer Packet ...............................................................................................5-39 Sector ID ...................................................................................................................5-39 Cause.........................................................................................................................5-39 Mobile Identity (MN ID) ..........................................................................................5-40 PDSN IP Address......................................................................................................5-40 Access Network Identifiers.......................................................................................5-41 Session State Information Record.............................................................................5-41 Information Element Identifiers................................................................................5-43 A14 Message Type ...................................................................................................5-43 ATI (Access Terminal Identifier) .............................................................................5-44 Correlation ID ...........................................................................................................5-46 Sector ID ...................................................................................................................5-46 Sector ID List............................................................................................................5-47 Session State Information Record.............................................................................5-47 A14 Indicators...........................................................................................................5-47 Cause.........................................................................................................................5-48 Security Layer Packet ...............................................................................................5-49 Message Sequence ....................................................................................................5-49 Upper Old UATI Length...........................................................................................5-50 Upper Old UATI .......................................................................................................5-50 UATI Subnet Mask ...................................................................................................5-50 Ax Traffic ID ............................................................................................................5-50 Access Network Identifiers.......................................................................................5-52 System Time .............................................................................................................5-52 UATI Color Code .....................................................................................................5-52 vii

5.2.2

A14 Information Element Definitions ........................................................................................5-43 5.2.2.1 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.5 5.2.2.6 5.2.2.7 5.2.2.8 5.2.2.9 5.2.2.10 5.2.2.11 5.2.2.12 5.2.2.13 5.2.2.14 5.2.2.15 5.2.2.16 5.2.2.17 5.2.2.18

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35

May 2007

5.2.3

A15 Information Element Definitions ........................................................................................5-54 5.2.3.1 5.2.3.2 5.2.3.3 5.2.3.4 5.2.3.5 5.2.3.6 5.2.3.7 5.2.3.8 Information Element Identifiers................................................................................5-54 A15 Message Type ...................................................................................................5-54 ATI (Access Terminal Identifier) .............................................................................5-54 Correlation ID ...........................................................................................................5-55 Sector ID ...................................................................................................................5-55 Sector ID List............................................................................................................5-56 Session State Information Record.............................................................................5-56 A15 Indicators...........................................................................................................5-57

5.3 5.3.1

Timer Definitions........................................................................................................................5-58 Timer Descriptions......................................................................................................................5-58 5.3.1.1 5.3.1.2 5.3.1.3 5.3.1.4 5.3.1.5 5.3.1.6 5.3.1.7 5.3.1.8 5.3.1.9 5.3.1.10 5.3.1.11 5.3.1.12 5.3.1.13 5.3.1.14 5.3.1.15 5.3.1.16 5.3.1.17 5.3.1.18 5.3.1.19 Timer TA13req ..............................................................................................................5-58 Timer TA13res ..............................................................................................................5-58 Timer Tgu14 ................................................................................................................5-58 Timer Tauthreq14 ...........................................................................................................5-58 Timer Tauthcom14 ..........................................................................................................5-59 Timer Tauthcomp14 .........................................................................................................5-59 Timer Tauthfail14 ...........................................................................................................5-59 Timer Trelcom14 ............................................................................................................5-59 Timer Tsu14 ................................................................................................................5-59 Timer T14-UATI-Req .......................................................................................................5-59 Timer T14-UATI-Assign ....................................................................................................5-59 Timer T14-UATI-Comp .....................................................................................................5-59 Timer Tpage14 ..............................................................................................................5-59 Timer Tprsp14 ..............................................................................................................5-59 Timer Tpreq14 ..............................................................................................................5-60 Timer Tkareq14 .............................................................................................................5-60 Timer Trel14 ................................................................................................................5-60 Timer Tprsp15 ..............................................................................................................5-60 Timer Tpreq15 ..............................................................................................................5-60

Annex A Annex B Annex C Annex D

A8-A9 (AN - PCF) Interface Change Text ............................................................................ A-1 A10-A11 (AN/PCF - PDSN) Interface Change Text ............................................................. B-1 A12 RADIUS Attributes ........................................................................................................ C-1 Revision History .................................................................................................................... D-1

viii

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

A.S0007-A v3.0 HRPD IOS

Table of Figures

Figure 1.5-1 Figure 1.6-1 Figure 2.3-1 HRPD IOS Alternative Architecture Reference Model ...................................................1-6 Packet Data Mobility Architecture for HRPD .................................................................1-6 RADIUS Protocol Reference Model ...............................................................................2-2

Figure 3.1.1-1 Initial AT Origination with HRPD Session Establishment and Key Exchange...............3-1 Figure 3.1.2-1 Initial AT Origination - Unsuccessful Terminal Authentication .....................................3-5 Figure 3.2.1-1 Re-authentication of an AT in Dormant State without Paging Response........................3-8 Figure 3.2.2-1 Re-authentication of an AT in Dormant State with Paging Response ...........................3-10 Figure 3.2.3-1 Re-authentication of an AT in Active State ...................................................................3-12 Figure 3.3.1.1-1 Successful Network Initiated Call Re-activation (Paging Type 0) ................................3-14 Figure 3.3.1.2-1 Successful Network Initiated Call Re-activation (Paging Type 1) ................................3-16 Figure 3.3.2-1 AT Initiated Call Re-activation from Dormant State (Existing HRPD Session) ...........3-18 Figure 3.4.1-1 AT Initiated Connection Release ...................................................................................3-19 Figure 3.4.2-1 AN Initiated Connection Release...................................................................................3-19 Figure 3.4.3-1 PCF Initiated Connection Release .................................................................................3-20 Figure 3.4.4-1 Connection Release Caused by Air Link Lost ...............................................................3-20 Figure 3.5.1-1 AT Initiated HRPD Session Release (A8 Connection Exists) .......................................3-22 Figure 3.5.2-1 AT Initiated HRPD Session Release (A8 Connection does not Exist) ..........................3-23 Figure 3.5.3-1 AN Initiated HRPD Session Release (A8 Connection Exists) ......................................3-24 Figure 3.5.4-1 PCF Initiated HRPD Session Release (A8 Connection Exists) .....................................3-25 Figure 3.5.5-1 PCF Initiated HRPD Session Release (A8 Connection does not Exist) ........................3-26 Figure 3.6-1 PDSN Initiated Packet Data Session Release ................................................................3-27 Figure 3.7.1-1 Inter-PCF/Intra-PDSN Dormant PCF-PCF HO - Successful Operation........................3-28 Figure 3.7.2-1 Inter-PCF/Intra-PDSN Dormant PCF-PCF HO - Transfer Failure................................3-30 Figure 3.8.1-1 Activation /De-activation of Data Flow During Active HRPD Session ........................3-31 Figure 3.8.2-1 Session Information Update During an Active HRPD Session .....................................3-32 Figure 3.9.1-1 Route Updating of a Dormant AT .................................................................................3-33 Figure 3.9.2-1 Session Keep Alive Procedure of a Dormant AT ­ Initiated by the PCF ......................3-34 Figure 4.1.1-1 1x to HRPD Dormant Packet Data Session HO - Existing HRPD Session .....................4-1 Figure 4.1.2-1 1x to HRPD Dormant Packet Data Session Handoff - New HRPD Session ...................4-3 Figure 4.1.3-1 HRPD to 1x Dormant Packet Data Session Handoff.......................................................4-7 Figure 4.2.1-1 Voice Call Termination During Active HRPD Packet Data Session (Inter-PCF) ...........4-9 Figure 4.2.2-1 AT Leaving During an Active HRPD Data Session ......................................................4-11 Figure 4.2.3-1 Voice Call Termination During Active HRPD Packet Data Session (Intra-PCF) .........4-12 Figure 4.4-1 Figure C-1 Terminal Based Status Management (Using Feature Invocation) .................................4-15 3GPP2 RADIUS Attribute Format ................................................................................. C-1

ix

A.S0007-A v3.0 HRPD IOS

1

May 2007

Foreword

While based on [11], the interfaces defined in this document are compatible with a TIA/EIA/IS-2001 or higher release. This document describes the protocol and some generic procedures to support High Rate Packet Data (HRPD) IOS features. Conformance to the IOS may be claimed on a feature-by-feature and/or interface-by-interface basis. If conformance on a given interface is claimed for the HRPD IOS feature, it shall be supported as defined in this standard. Features: Terminal authentication Data delivery Session handoff between ANs Status management

2 3 4 5 6

7 8 9 10 11 12 13

x

May 2007

1

A.S0007-A v3.0 HRPD IOS

1 Introduction

1.1 Scope

2

3

4 5 6

This document provides an inter-operability specification for a Radio Access Network (RAN) that supports HRPD. This document contains message procedures and formats necessary to obtain this interoperability.

7 8 9 10 11 12 13 14

1.2

Document Convention

"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 several possibilities is recommended as particularly suitable, without mentioning or excluding others; that a certain course of action is preferred but not necessarily required; or (in the negative form) that a certain possibility or course of action is discouraged but not prohibited. "May" and "need not" indicate a course of action permissible within the limits of the standard. "Can" and "cannot" are used for statements of possibility and capability, whether material, physical, or causal.

15 16

1.3

References

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40

1.3.1

TIA / EIA

For ease of cross referencing, the Telecommunications Industry Association (TIA) / Electronics Industry Association (EIA) references provided in this section are aligned with the 3GPP2 references, provided in section 1.3.2. For consistency between RAN specifications, the most commonly referenced documents [1~17] are maintained or left as "Reserved" if not used in this specification. [1] cdma2000 Standards for Spread Spectrum Systems Release A: TIA/EIA/IS-2000.1-A, Introduction for cdma2000 Standards for Spread Spectrum Systems, March 2000. TIA/EIA/IS-2000.2-A-1, Physical Layer Standard for cdma2000 Spread Spectrum Systems, November 2000. TIA/EIA/IS-2000.3-A-1, Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum Systems, November 2000. TIA/EIA/IS-2000.4-A-1, Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems, November 2000. TIA/EIA/IS-2000.5-A-1, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems, November 2000. TIA/EIA/IS-2000.6-A-1, Analog Signaling Standard for cdma2000 Spread Spectrum Systems, November 2000. [2-6] [7] [8] [9] [10] Reserved. TIA/EIA-95-B, Mobile Station-Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Systems, March 1999. IS-707-A-2, Data Service Options for Spread Spectrum Systems, March 2001. TIA/EIA/IS-835-A, cdma2000 Wireless IP Network Standard, May 2001. TIA/EIA/IS-856, cdma2000 High Rate Packet Data Air Interface Specification, February 2001. 1-1

A.S0007-A v3.0 HRPD IOS

1 2 3

May 2007

[11] [12-17] 1.3.2

TIA/EIA/IS-2001-A, Interoperability Specification (IOS) for CDMA 2000 Access Network Interfaces, May 2001. Reserved. 3GPP2

4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

The 3GPP2 references are aligned with the TIA/EIA references of Section 1.3.1 and are provided here for information and cross reference purposes. [1] cdma2000 Standards for Spread Spectrum Systems Release A: 3GPP2 C.S0001-A, Introduction to cdma2000 Standards for Spread Spectrum Systems, June 2000. 3GPP2 C.S0002-A-1, Physical Layer Standard for cdma2000 Spread Spectrum Systems, October 2000. 3GPP2 C.S0003-A-1, Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum Systems, October 2000. 3GPP2 C.S0004-A v2.0, Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems, October 2000. 3GPP2 C.S0005-A-1, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems, October 2000. 3GPP2 C.S0006-A, Analog Signaling Standard for cdma2000 Spread Spectrum Systems, July 2000. [2-6] [7] [8] [9] [10] [11] [12] [13-17] 1.3.3 [18] [19] [20] [21] [22] [23] [24] [25] Reserved. Reserved. Note: there is no 3GPP2 equivalent for TIA/EIA-95-B. 3GPP2 C.S0017-0-2 v2.0, Data Service Options for Spread Spectrum Systems, August 2000. 3GPP2 P.S0001-A, Wireless IP Network Standard, July 2000. 3GPP2 C.S0024 v3.0, cdma2000 High Rate Packet Data Air Interface Specification, December 2001. 3GPP2 A.S0001-A v2.0, 3GPP2 Access Network Interfaces Interoperability Specification, June 2001. A.R0011, A Report on Issues Identified with IOS v4.1, August 2002. Reserved. Other RFC 1321, MD5 Message-Digest Algorithm, April 1992. RFC 1661, Point-to-Point Protocol, July 1994. RFC 1662, PPP in HDLC-Like Framing, July 1994. RFC 1701, Generic Routing Encapsulation (GRE), October 1994. RFC 1750, Randomness Recommendations for Security, December 1994. RFC 1994, PPP Challenge Handshake Authentication Protocol (CHAP), August 1996. RFC 2486, The Network Access Identifier, January 1999. RFC 2865, Remote Authentication Dial In User Service (RADIUS), June 2000.

30 31 32 33 34 35 36 37 38

1-2

May 2007

1

A.S0007-A v3.0 HRPD IOS

1.4

Terminology

2

3

1.4.1

Acronyms

AAA ACCM AN ANID AT BS CANID CHAP CVSE HRPD IMSI IOS LCP MAC MEI MN ID MS MSC NAI NID PANID PCF PDSN PPP PZID RADIUS RAN SC/MM SID SKey UATI

4

Authentication, Authorization and Accounting Async-Control-Character-Map Access Network Access Network Identifiers Access Terminal Base Station Current Access Network Identifiers Challenge Handshake Authentication Protocol Critical Vendor/Organization Specific Extension High Rate Packet Data International Mobile Subscriber Identity Inter-Operability Specification Link Control Protocol Medium Access Control Mobility Event Indicator Mobile Node Identification Mobile Station Mobile Switching Center Network Access Identifier Network Identification Previous Access Network Identifiers Packet Control Function Packet Data Serving Node Point-to-Point Protocol Packet Zone Identification Remote Authentication Dial-In User Service Radio Access Network Session Control / Mobility Management System Identification Session Key Unicast Access Terminal Identifier

5 6 7

1.4.2

Definitions The HRPD stream whose end-points are the access terminal and the access network (radio network). This stream is used for terminal authentication.

Access Stream

1-3

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49

May 2007 The network equipment providing data connectivity between a packet switched data network (typically the Internet) and the access terminals. An access network is equivalent to a base station in 1x systems. A device providing data connectivity to a user. An access terminal may be connected to a computing device such as a laptop personal computer or it may be a self-contained data device such as a personal digital assistant. An access terminal is equivalent to a mobile station in 1x systems. An entity that performs terminal authentication and authorization functions for the AN. A connection, in this specification, refers to either an air interface connection or a signaling or user traffic connection in the RAN. An air interface connection is a particular state of the air-link in which the access terminal is assigned a Forward Traffic Channel, a Reverse Traffic Channel and associated Medium Access Control (MAC) Channels. During a single HRPD session the AT and the AN can open and can close a connection multiple times. A signaling or user traffic connection is a particular state shared between two nodes in the RAN or between a node in the RAN and a network entity outside the RAN. Examples of a connection in the RAN are A8 and A10 connections, which are used for user traffic. A device capable of operating on both 1x and HRPD ANs. The HRPD stream used when exchanging data between the AT and the PDSN. An HRPD session refers to a shared state between the AT and the AN. This shared state stores the protocols and protocol configurations that were negotiated and are used for communications between the AT and the AN. Other than to open a session, an AT cannot communicate with an AN without having an open session. Note that it is possible that the A10/A11 connection is not established even though the HRPD session is established. Refer to [10], section 1.9. The PCF definition is provided in [11]. In addition, the PCF for this specification logically contains the SC/MM function. This additional functionality is HRPD specific and does not apply to any operations and procedures as specified in [11]. Refer to the definition of SC/MM function. An instance of use of packet data service by a mobile user. A packet data session begins when the user invokes packet data service. A packet data session ends when the user or the network terminates packet data service. During a particular packet data session, the user may change locations but the same IP address is maintained. Refer to [11], section 1.6.2. SC/MM (Session Control and Mobility Management) is logically located in the PCF and includes the following functions: · Storage of HRPD session related information: This function keeps HRPD session related information (e.g., Keep Alive timer, MNID, mapping between MNID and UATI, etc.) for dormant ATs. · Assignment of UATI (Unicast AT identifier): This function assigns a new UATI to an AT. · Terminal Authentication: This function performs the terminal authentication procedure. This function judges whether an AT should be authenticated or not when the AT is accessing the HRPD RAN. The SC/MM performs PPP procedures for terminal authentication. 1-4

Access Network (AN)

Access Terminal (AT)

AN-AAA Connection

Hybrid MS/AT Service Stream HRPD session

PCF

Packet Data Session

SC/MM function:

May 2007

1 2 3 4 5

A.S0007-A v3.0 HRPD IOS · Mobility Management: This function manages the location of an AT. The location information of the AT is obtained via distance-based registration. This function may perform paging procedures based on location information.

Terminal Authentication:

A procedure in which the AT is authenticated by the AN-AAA.

6

1.5

A8

HRPD IOS Alternative Architecture Reference Model

The A8 interface carries user traffic between the Access Network (AN) and the Packet Control Function (PCF). For A8 descriptions, refer to section 2.1. A8 interface changes required for HRPD are provided in Annex A. The A9 interface carries signaling information between the AN and the PCF. For A9 descriptions, refer to section 2.1. A9 interface changes required for HRPD are provided in Annex A. The A10 interface carries user traffic between the PCF and the PDSN. For A10 descriptions, refer to section 2.2. A10 interface changes required for HRPD are provided in Annex B. The A11 interface carries signaling information between the PCF and the PDSN. For A11 descriptions, refer to section 2.2. A11 interface changes required for HRPD are provided in Annex B. The A12 interface carries signaling information related to terminal authentication between the SC/MM function in the PCF and the AN-AAA (Authentication, Authorization and Accounting entity). For a description of the A12 interface, refer to section 2.3. The A13 interface carries signaling information between the SC/MM function in the source PCF and the SC/MM function in the target PCF. For a description of the A13 interface, refer to section 2.4. The A14 interface carries signaling information between the SC/MM function in the PCF and the AN. For a description of the A14 interface, refer to section 2.5. The A15 interface carries signaling information between ANs when inter-AN paging is used. For a description of the A15 interface, refer to section 2.6. The Ax interface carries user traffic between the SC/MM function in the PCF and the AN. For a description of the Ax interface, refer to section 2.7.

7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

The interfaces defined in this specification are described as follows.

A9

A10

A11

A12

A13

A14 A15 Ax

The HRPD IOS messaging and call flows are based on the Alternative Architecture Reference Model shown in Figure 1.5-1.

1-5

A.S0007-A v3.0 HRPD IOS

A8 A9 A14 Ax

May 2007

Air Interface

Source Access Network (AN)

Source PCF SC/MM Function

A10 PDSN A11

Access Terminal (AT)

A15

A13

A12

AN AAA

Target Access Network (AN)

SC/MM Function Target PCF

1 2

Figure 1.5-1

HRPD IOS Alternative Architecture Reference Model

3

1.6

HRPD Micro-Mobility and Macro-Mobility Concepts

4

Figure 1.6-1 provides a conceptual view of levels of HRPD packet data mobility.

Home Agent Mobility between PDSNs (Mobile IP) PDSN PDSN Mobility between PCFs (A10/A11/A13 Interfaces) PCF PCF PCF Mobility between ANs (A8/A9/A14 Interfaces) AN AN AN AN

5 6

Figure 1.6-1 · · ·

Packet Data Mobility Architecture for HRPD

7 8 9

The A8/A9/A14 interfaces support mobility between ANs under the same PCF. The A10/A11/A13 interfaces support mobility between PCFs under the same PDSN. Mobile IP supports mobility between PDSNs under the same Home Agent.

10

1.7

Compatibility with IS-2001 Standards

11 12 13 14 15 16 17 18 19

The HRPD IOS interface, as defined in this specification, is compatible with TIA-2001-A, with the provision that the HRPD capabilities are the same as those supported by the interoperability specification, for the access network(s) in use. This standard does not assume support for TIA-2001-A features. For example, when inter-operating with a TIA/EIA/IS-2001 system, the portions of TIA-2001-A related to concurrent services and support for Short Data Bursts are not applicable. Note: When the procedures between TIA/EIA/IS-95-B or 1x and HRPD systems differ, the HRPD procedures are identified separately within this specification. When the TIA/EIA/IS-2001 text is applied to the HRPD RAN specification, the procedures related to the MSC shall be ignored. Hard Handoff procedures, as defined in [11], are not applicable to HRPD.

1-6

May 2007

1 2 3

A.S0007-A v3.0 HRPD IOS

In the event that message formats or procedures defined in this standard cause an incompatibility with an entity compliant to an earlier version of this standard, the message formats or procedures of the earlier version shall take precedence.

4 5 6 7 8 9 10 11 12 13 14 15 16

1.8

Message Body, Coding, Ordering, and Interpretation of Elements

For interfaces common to 1x, the guidelines in the base 1x text apply. Refer to Annexes for more information. For each HRPD IOS-unique interface's message, there are a number of information elements that are individually defined in section 5.2. Each information element in a given message is tagged with a reference in section 5.1, a direction indication (i.e., some elements within a message are bi-directional and others are not), and a mandatory/optional type (M/O) indicator. Information elements that are marked as optional carry an additional indication of being either required (R) or conditional (C) (refer to below). Some information elements are reused in multiple messages. The DIRECTION indication associated with each information element pertains to the use of that particular information element when used with the particular message (i.e., use of the information element may be different in other messages). The format of the DIRECTION indication is as follows:

Source -> Target Target -> Source

17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

Element flows from the Source to the Target Element flows from the Target to the Source

The inclusion of information elements in each message is specified as follows: M O R C Information elements which are mandatory for the message. Information elements which are optional for the message. Required in the message whenever the message is sent. Conditionally required. The conditions for inclusion of this element are defined in the operation(s) where the message is used and in footnotes associated with the table defining the order of information elements in the message.

Information elements which are mandatory for a given message shall be present, and appear in the order shown in the message definitions. Information elements which are optional for a given message are included as needed for specific conditions. When included, they shall appear in the order shown in the message definition. An information element may be mandatory for some messages and optional for other messages. The following conventions are assumed for the sequence of transmission of bits and bytes: · Each bit position is marked as 0 to 7. For HRPD IOS-unique interfaces, bit 0 is the least significant bit and is transmitted first. · In a message, octets are identified by number. Octet 1 is transmitted first, then octet 2, etc. For variable length elements, a length indicator is included. This indicates the number of octets following in the element. Information elements shall always use the same Information Element Identifier for all occurrences on a specific HRPD interface. Insofar as possible, the same Information Element Identifier shall be used for a given information element when it is used on more than one interface. For future expansion purposes, some of these information elements have fields within them that have been reserved. All reserved bits are set to 0, unless otherwise indicated. To allow compatibility with future implementation, messages shall not be rejected simply because a reserved bit is set to `1'. The bitmap tables in the message subsections of section 5.1 are patterned after the format for the information elements of section 5.2 and use the following conventions: 1-7

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

May 2007

Element Name{<# instances>: = Name of information element. Different elements within a message are separated by double lines. Fields within elements are separated by single lines. Octets are renumbered at the beginning of every element.

[<values>] } Element Name

= Set of allowed values. The number of instances of an element is 1 by default. If the Element Name{<# instances ... }Element Name notation is used, the <# instances> notation indicates: n n+ 1..n = exactly n occurrences of the element = n or more occurrences of the element = 1 to n inclusive occurrences of the element

label {<# instances>: <octet 1> <octet m> } label = Number of instances of the bracketed set of fields where <# instances> notation indicates: n n+ 1..n ssss ssss ... ssss ssss = Variable length field. = exactly n occurrences of the field = n or more occurrences of the field = 1 to n inclusive occurrences of the field

24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

1.9

Forward Compatibility Guidelines

This standard is intended to evolve to accommodate new features and capabilities. To ensure that equipment implemented to one revision level interoperates with equipment implemented to later revision levels, the following guidelines are defined for the processing of messages and for the development of messages in future revisions of this standard. Unexpected signaling information may be received at an entity due to differing revision levels of signaling protocol at different entities within a network: an entity using a more enhanced version of the protocol may send information to an entity implemented at a lower level of the protocol which is outside the protocol definition supported at that receiving entity. It may happen that an entity receives unrecognized signaling information, i.e., messages, element types or element values. This can typically be caused by the upgrading of the protocol version used by other entities in the network. In these cases the following message processing guidelines are invoked to ensure predictable network behavior. The sending entity shall send messages that are correctly formatted for the version of the IOS implemented by the sending entity.

1-8

May 2007

1

A.S0007-A v3.0 HRPD IOS

1.10

Message Processing Guidelines

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

The following message processing guidelines apply to HRPD IOS-unique interfaces unless overridden by explicit processing directions in other places within this standard. In the guidelines in this section, "optional" includes both "optional ­ conditional" and "optional ­ required" information elements as indicated in the message tables in section 5.1. 1. If a message is received containing a Message Type value which is not defined for the revision level implemented then the message shall be discarded and ignored. There shall be no change in state or in timers due to receipt of an unknown message. 2. If a message is received without an expected mandatory information element for the revision level implemented then the message shall be discarded and ignored. There shall be no change in state or in timers due to receipt of the message. 3. If a message is received that contains an information element which is defined for the revision level implemented but contains invalid values in some fields, these fields shall be ignored and the remainder of the information element processed to the extent possible. The message and all other information elements shall be processed to the extent possible. Failure handling may be initiated if call processing cannot continue. Also refer to message processing guidelines 9 and 10. 4. If a message is received that contains an Information Element Identifier which is not defined for the revision level implemented then that element shall be discarded and ignored. The message shall be processed to the extent possible. Failure handling may be initiated if call processing cannot continue. 5. If a known but unexpected optional information element is received, that information element shall be ignored. The message and all other information elements shall be processed. 6. If a message is received without an expected optional information element the message shall be processed to the extent possible. Failure handling may be initiated if call processing cannot continue. 7. If a field within a received information element contains a value which is specified as "reserved" or is otherwise not defined in the revision level implemented, this field shall be ignored and the remainder of the information element processed to the extent possible. In this situation, all other information elements shall be processed to the extent possible. 8. Octets and bits designated as "Reserved" or which are undefined for the revision implemented shall be set to zero by a sending entity and ignored by a receiving entity even if the value is nonzero. 9. If an element is received containing a field that is larger than expected, i.e., is indicated as having more bits/octets than expected, then the expected bits/octets of that field shall be processed to the extent possible and the additional bits/octets shall be ignored. 10. If an element is received containing a field that is smaller than expected, i.e., is indicated as having fewer bits/octets than expected, then the length field or other indicator shall be considered correct and the bits/octets actually present in the element shall be processed to the extent possible. Failure handling may be initiated if call processing cannot continue.

37

1.11

Message Definition Guidelines

38 39 40 41 42 43 44

1. New messages shall have a Message Type that has never been previously used on that interface. 2. Information Element Identifiers shall not be reused in future revisions. 3. Defined valid values of Information Elements may be changed in future revisions. The new version shall define the error handling when previously valid values are received. 4. Octets and bits which are undefined or which are defined as reserved may be used in future revisions. 5. The Mandatory/Optional designation of Information Elements within a message shall not change. 6. Mandatory Information elements shall be sent in the order specified in section 5.1. 1-9

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9

May 2007

7. New optional Information Elements in a message shall be defined after all previously defined optional Information Elements. 8. All new Information Elements shall be defined with a length field. Note that most existing Information Elements have 1 octet length fields but some existing Information Elements have 2 octet length fields. Information Element Identifier values in the range A0H-BFH inclusive shall be defined to have a 2 octet length field. All other new Information Element Identifier values shall be defined to have a 1 octet length field. 9. New information may be added to the end of an existing Information Element, provided that the Information Element is defined with a length field.

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

1.12

HRPD IOS Assumptions

The following assumptions are made regarding PCF, SC/MM, AN and AT behavior: 1. A packet data session may transition from a serving 1x system to a serving HRPD system and from a serving HRPD system to a serving 1x system. 2. A unique value, 59 (3BH), is used in the Service Option fields in accounting records transported on the A9 and A11 interfaces to identify accounting records associated with HRPD packet data service. 3. For the case of dormant inter-AN inter-PCF handoff, the target PCF may use the PDSN address received from the source PCF to send the A11-Registration Request message. Otherwise, the target PCF shall use the PDSN selection algorithm (if supported and if the IMSI is available) or internal algorithms to select a PDSN. 4. The AT may transition a packet data session from a serving HRPD system to a serving 1x system and back to a serving HRPD system. Therefore, following a dormant handoff, the target AN shall send the PANID received from the AT to the target PCF. Otherwise if the AT does not send the PANID or the AN chooses not to request this information from the AT, then the target PCF may use the PANID received in the A13-Session Information Response message from the source PCF. 5. The AT shall support Challenge Handshake Authentication Protocol (CHAP) terminal authentication. In this case, the AT shall send a Network Access Identifier (NAI) of the form specified in [24]. 6. For terminal authentication, the generation of the NAI and password are the responsibility of the service provider. The NAI and password should be chosen and managed using procedures that minimize the likelihood of compromise. 7. If the terminal authentication feature is used, the PCF shall always propose CHAP as a PPP option in an initial Link Control Protocol (LCP) Configure-Request during the PPP establishment. 8. The Mobile Node Identification (MN ID) that is used by the PCF on A10/A11 messages is unique within the operator's network, and is determined as follows: · · If the HRPD PCF uses the terminal authentication feature, the MN ID field shall be set to the MN ID value returned by the AN-AAA (e.g., IMSI) following successful terminal authentication. Otherwise, the PCF shall set the MN ID field to a value that conforms to a valid MN ID format (i.e., IMSI format). In this case, the MN ID is determined by other means.

9. After the AT indicates it is ready to exchange data on the access stream, the PCF initiates PPP procedures according to [19]. 10. The AT may support packet data service as specified in [9]. 11. Session information (UATI, authentication keys) for an active HRPD session shall be maintained in the SC/MM. This information may also be maintained in the AN. 12. The SC/MM and the PCF can communicate directly with each other. The interface between the PCF and the SC/MM is considered beyond the scope of the standard. 1-10

May 2007

1 2 3

A.S0007-A v3.0 HRPD IOS

13. One subnet (refer to [10]) shall not be covered by multiple PCFs. 14. When inter-AN paging is used, all ANs involved in the paging are connected to the same PCF.

1-11

A.S0007-A v3.0 HRPD IOS

1 2

May 2007 No text.

1-12

May 2007

1

A.S0007-A v3.0 HRPD IOS

2 HRPD IOS Interfaces

This section describes the RAN interfaces associated with this specification. When looking at procedures in TIA-2001-A that are applicable to this specification, the terms in the left column of the table shall be mapped to the terms in the right column in the table. Otherwise, the terms in the left column of the table shall be mapped to the corresponding terms in the right column when interpreting Annex A and Annex B of this specification. 1x Term BS Base Station MS Mobile Station HRPD Term AN Access Network AT Access Terminal

2 3 4 5 6

7

2.1

A8-A9 (AN - PCF) Interface

8 9

The specification for the A8-A9 interface is defined in [11] with identified bug-fixes applicable to this interface defined in [12]. Updates to address HRPD are included in Annex A.

10 11 12 13

2.2

A10-A11 (PCF - PDSN) Interface

The specification for the A10-A11 interface is defined in [11] with identified bug-fixes applicable to this interface defined in [12]. While no new signaling information is defined for the interface between the PCF and the PDSN, updates to address HRPD are included in Annex B.

14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

2.3

A12 (PCF - AN-AAA) Interface and Terminal Authentication

The SC/MM function is assumed to be logically contained in the PCF. In this section, it is assumed that the A12 interface terminates at the SC/MM and PPP procedures for terminal authentication also terminate at the SC/MM. References to `PCF' in this section should take this fact into consideration. The A12 interface between the SC/MM function of the PCF and the AN-AAA entities is used for the following purposes: 1. to transmit data used to perform terminal authentication (by authenticating the results of a CHAP challenge/response operation invoked by the PCF). 2. to return the MN ID that is used on the A10/A11 interfaces (following successful terminal authentication of the AT). This identifier permits handoffs of PDSN packet data sessions between PCFs and between HRPD and 1x systems. If terminal authentication is not used by an HRPD system, the MN ID that is used by the PCF on the A10/A11 interface is determined by other means beyond the scope of this specification. The A12 interface conforms to the Remote Authentication Dial-In User Service (RADIUS) protocol as defined in [18] and [25]. The interface is shown in Figure 1.5-1. The A12 interface consists of the following messages: · · · A12 Access-Request A12 Access-Accept A12 Access-Reject

Note: In the call flows of this document these message names are prefixed with "A12", to conform to IOS notation convention. Figure 2.3-1 shows the protocol reference model for the A12 interface. The AN-AAA in the visited access provider and home access provider IP networks communicate via AN-AAA proxy servers and one or more AN-AAA brokers. Note: The use of AN-AAA brokers is optional.

2-1

A.S0007-A v3.0 HRPD IOS

May 2007

RADIUS

RADIUS RADIUS

RADIUS RADIUS

RADIUS

UDP IP Link Layer PL

UDP IP Link Layer PL

UDP IP Link Layer PL

UDP IP Link Layer PL

UDP IP Link Layer PL

UDP IP Link Layer PL Home AN-AAA

PCF

1 2

Visited AN-AAA

Broker AN-AAA (optional)

Figure 2.3-1 2.3.1 2.3.1.1 PPP Session Establishment

RADIUS Protocol Reference Model

3

4 5 6 7 8 9

The PCF shall initiate PPP procedures according to [19] by sending an LCP Configure-Request. PPP shall support transparency in accordance with section 4.2 of [20]. The PCF and AT shall attempt to negotiate a control character mapping, with the minimum number of escape characters by proposing an AsyncControl-Character-Map (ACCM) of 0x 00000000. Additionally, if no PPP session is present, the PCF may re-authenticate the AT by reinitiating the PPP session. 2.3.1.2 Termination

10 11 12 13

The PCF may release the PPP connection after the terminal authentication of the AT has been performed. The PCF may support a PPP inactivity timer for each PPP session. When the inactivity timer expires, the PCF shall terminate the PPP session. 2.3.1.3 Terminal Authentication

14 15 16 17 18 19 20 21 22 23 24

The AT shall support CHAP for the PPP instance on the access stream. If the PCF supports terminal authentication, the PCF shall support CHAP for the PPP instance on the access stream. In this case, the PCF shall always propose CHAP as a PPP option in an initial LCP Configure-Request during the PPP establishment. The AN may discard or buffer data received on the service stream during the terminal authentication procedure. The PCF shall not forward data to the AN during the terminal authentication procedure. The terminal authentication procedure is successful when; · the AT receives a CHAP success, or · the AT receives the indication for opening service stream (e.g., receiving DataReady message or RLP packets). 2.3.2 AN-AAA Support

25 26 27 28 29 30 31

If the PCF supports terminal authentication and the A12 interface, the PCF shall support the RADIUS client protocol in accordance with [25] and shall communicate user CHAP terminal authentication information to the visited AN-AAA in an Access-Request message on the A12 interface. For an AN-AAA to recognize that the transaction is related to terminal authentication, the Access-Request message may contain an additional 3GPP2 vendor specific attribute. Refer to Annex C, RADIUS Attributes. If the Access-Request message on the A12 interface contains a 3GPP2 Vendor Specific Attribute, the proxy 2-2

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

A.S0007-A v3.0 HRPD IOS

AN-AAA shall include the attribute in the Access-Request message forwarded to the home AN-AAA on the A12 interface. On receipt of the AT's CHAP response, the PCF shall send an Access-Request message, on the A12 interface, containing at a minimum: · User-Name (1) 1 = NAI · CHAP-Password (3) = CHAP ID and CHAP-response · NAS-IP-Address (4) = IP address of PCF · CHAP-Challenge (60) = challenge value issued by PCF In addition, the Access-Request message may optionally contain an HRPD Terminal Authentication Indicator in a RADIUS vendor specific extension (defined in Annex C), which is used to indicate the purpose of the access request. Note: The CHAP terminal authentication password should be cryptographically strong. One recommendation for password generation can be found in [21], Randomness Recommendations for Security, section 7.1. Upon successful terminal authentication the visited AN-AAA shall send an Access-Accept message to the PCF on the A12 interface. The Access-Accept message shall contain at a minimum the RADIUS Callback-Id attribute (Type=20) populated with the MN ID (e.g., IMSI) and the String field shall be set as follows: 0 1 2 3 4 5 6 7 Octet 1

ASCII encoded MN ID Type [30H denotes IMSI] ASCII encoded most significant Identity Digit = [30-39H] ASCII encoded least significant Identity Digit = [30-39H]

19 20 21 22 23 24 25 26 27 28 29

N

2.3.3

AN-AAA Requirements

The AN-AAA shall act as a RADIUS server and shall follow the guidelines specified in [25]. If the PCF performs terminal authentication using CHAP, the AN-AAA receives a RADIUS AccessRequest message on the A12 interface from the PCF with CHAP terminal authentication information. If the AN-AAA does not have the authority to accept/deny the request, it forwards the request to the home network or a peer (e.g., a broker), in accordance with [25]. In this case, the AN-AAA later receives an Access-Accept message from the home or broker network. The AN-AAA shall then send the AccessAccept message to the PCF, on the A12 interface. Communications between AN-AAAs may optionally be protected with IP security. The establishment of this security association is outside the scope of this standard. Refer also to [25] for additional RADIUS security requirements.

1

The numbers in this list correspond to the RADIUS attribute type defined in [25].

2-3

A.S0007-A v3.0 HRPD IOS

May 2007

1

2.4

A13 (PCF - PCF) Interface

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33

The A13 interface carries HRPD session related information between the SC/MM function of the source PCF and the SC/MM function of the target PCF. The information exchanged is divided up into information in the target to source direction, and source to target direction. The information content in the target to source direction is as follows: · Unicast Access Terminal Identifier (UATI). This is the UATI determined by the target PCF using the UATI Color Code and UATI024 received from the AT, which allows the source PCF to determine the session configuration parameters that are requested by the target PCF. Note that some parts of the UATI determined by the target PCF may not be meaningful. However, it is assumed that the source PCF will have enough information to identify the corresponding session. · Security Layer Packet. This is the Security Layer packet, including protocol header and trailer, as received from the AT. · Sector ID. The target PCF shall set this field to the 128-bit identifier of the sector on which the UATIRequest message is received. The information content in the source to the target direction is as follows: · MN ID used by the source PCF over the A11 interface. This allows the target PCF to use the same MN Identifier from the previous A10 connection, once a new A10 connection has been setup. · Session Configuration Parameters. These parameters, including the air interface protocols states, allow the target AN to continue to use the air interface protocols previously negotiated between the AT and the source AN. · PDSN address. This IP v4 address allows the target PCF to reconnect (when possible) to the same PDSN without executing a PDSN re-selection algorithm (if specified) or an internal PDSN selection algorithm. The target PCF may use the PDSN address received from the source PCF to send the A11Registration Request message. Otherwise, the target PCF shall use the PDSN selection algorithm (if supported) or internal algorithms to select a PDSN. · PANID. This information allows the target PCF to inform the PDSN of the PANID, in the case that it is not provided by the AT over the air interface. The PANID, along with CANID information, allows the PDSN to determine if there is a need to do an agent advertisement. Note: The AT may transition a packet data session from a serving HRPD system to a serving 1x system and back to a serving HRPD system. Therefore, following a dormant handoff, the target PCF shall send the PANID received from the AT to the target PCF. Otherwise, if the AT does not send the PANID or the PCF chooses not to request this information from the AT, then the target PCF may use the PANID received in the A13-Session Information Response message from the source PCF. 2.4.1 A13 Interface Network/Transport Protocol Specification

34 35 36 37 38 39 40 41 42 43 44 45 46

Signaling over the A13 interface requires appropriate addressing and routing mechanisms to deliver messages. The IOS application is independent of the underlying physical transport medium, which is left to the discretion of operators and manufacturers. The signaling protocol stack available to operators and manufacturers for the A13 interface is: IOS Application UDP IP Link Layer Physical Layer The following UDP port value is reserved for signaling on the A13 interface: · A13 (PCF-to-PCF) 3125/udp - This is the well-known UDP port number to be used for signaling interconnection to another PCF.

2-4

May 2007

1 2 3 4 5 6 7 8

A.S0007-A v3.0 HRPD IOS

2.4.2

A13 Interface Procedures

This section describes the messages and procedures used between PCFs on an A13 connection. The information is exchanged via the following messages: · A13-Session Information Request · A13-Session Information Response · A13-Session Information Confirm · A13-Session Information Reject The procedures for how the target PCF discovers the source PCF and the UATI are not specified. 2.4.2.1 Session Information Procedure

9 10 11

Session information may be requested by the target PCF. For call flows associated with the A13 session information request, response, confirm and reject procedures, refer to sections 3.7.1and 3.7.2 . 2.4.2.1.1 A13-Session Information Request

12 13 14

The A13-Session Information Request message is sent by the target PCF to request information about an AT from a source PCF when the target PCF does not have this information. 2.4.2.1.1.1 Successful Operation

15 16 17 18 19 20 21

When the target PCF receives an A14-UATI Request message from the target AN for an AT for which the target PCF has not assigned a UATI, the target PCF attempts to retrieve session related information from the source PCF for that AT. The target PCF sends an A13-Session Information Request message to the source PCF to indicate the information requested. The target PCF shall include the determined UATI, Security Layer Packet and Sector ID. The target PCF then starts timer TA13req. Refer to section 5.1.1.1, A13-Session Information Request, for the format and content of this message. 2.4.2.1.1.2 Failure Operation

22 23 24 25 26

If timer TA13req expires, the target PCF may resend the A13-Session Information Request message a second time. If timer TA13req expires a second time or if the target PCF chooses not to resend the A13Session Information Request message, the target PCF shall begin a new session establishment with the AT. 2.4.2.1.2 A13-Session Information Response

27 28 29

The A13-Session Information Response message is used by the source PCF to respond to the target PCF's request to retrieve information about an AT. 2.4.2.1.2.1 Successful Operation

30 31 32 33 34 35 36 37

When the source PCF receives an A13-Session Information Request message it checks if the session information for the requested AT exists and if it can authenticate the target PCF request. After the source PCF has successfully authenticated the information contained in the A13-Session Information Request message, and if it has the requested session state information, the source PCF sends the requested information in an A13-Session Information Response message to the target PCF and starts timer TA13res. Upon receipt of the A13-Session Information Response message, the target PCF stops timer TA13req. Refer to section 5.1.1.2, A13-Session Information Response, for the format and content of this message. 2.4.2.1.2.2 None. 2-5 Failure Operation

38 39

A.S0007-A v3.0 HRPD IOS

1 2 3

May 2007

2.4.2.1.3

A13-Session Information Confirm

The A13-Session Information Confirm message is used by the target PCF to inform the source PCF that the target PCF has successfully received the session information about an AT. 2.4.2.1.3.1 Successful Operation

4 5 6 7 8 9

When the target PCF receives the A13-Session Information Response message from the source PCF with the requested AT information it shall send an A13-Session Information Confirm to the source PCF. Upon receipt of the A13-Session Information Confirm message, the source PCF shall remove the stored session information related to the AT in question and stop timer TA13res. Refer to section 5.1.1.3, A13-Session Information Confirm, for the format and content of this message. 2.4.2.1.3.2 None. 2.4.2.1.4 A13-Session Information Reject Failure Operation

10 11

12 13 14

The A13-Session Information Reject message is used by the source PCF to reject a request from the target PCF to retrieve session information from source PCF. 2.4.2.1.4.1 Successful Operation

15 16 17 18 19 20 21 22

When the source PCF receives an A13-Session Information Request message and it can not retrieve the session information or can not authenticate the identity of the target PCF, the source PCF responds by sending an A13-Session Information Reject message to the target PCF. Upon receipt of the A13-Session Information Reject message, the target PCF stops timer TA13req. After sending the A13-Session Information Reject message, the source PCF may retain the session information, if it exists. Refer to section 5.1.1.4, A13-Session Information Reject, for the format and content of this message. 2.4.2.1.4.2 None. Failure Operation

23 24

2-6

May 2007

A.S0007-A v3.0 HRPD IOS

1

2.5

A14 (AN - PCF) Interface

2 3 4 5 6 7 8 9 10

The A14 interface is used to transfer information between the AN and the SC/MM function of the PCF related to session and mobility procedures. The A14 interface supports following procedures: · UATI assignment · General updating · Terminal authentication · Session release · Session information updating · Paging 2.5.1 A14 Interface Network/Transport Protocol Specification

11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

To realize reliable transport, TCP may be used for the transport protocol. UDP may also be used for the transport protocol if the underlying transport guarantees low packet loss. The selection of TCP or UDP is left to the discretion of the operators and manufacturers. The signaling protocol stack available to operators and manufacturers for the A14 interface is: IOS Application TCP/UDP IP Link Layer Physical Layer When TCP is used as the transport, the PCF should wait for the request for the TCP connection from the AN. When UDP is used as the transport, the PCF and the AN shall use the same port number for sending and receiving messages over the A14 interface. The following TCP and UDP port values are reserved for signaling on the A14 interface: · A14 (AN-to-SC/MM) 3597/tcp ­ This is the well-known TCP port number to be used for signaling interconnection between the AN and the PCF. · A14 (AN-to-SC/MM) 3597/udp ­ This is the well-known UDP port number to be used for signaling interconnection between the AN and the PCF. 2.5.2 2.5.2.1 A14 Interface Procedures UATI Assignment Procedure

29

30 31 32

An AN request for an AT UATI assignment may be made to a PCF on the A14 interface. For call flows associated with the UATI assignment procedures, refer to sections 3.1.1, 3.1.2 and 4.1.2. 2.5.2.1.1 A14-UATI Request

33 34 35

The A14-UATI Request message is sent from the AN to the PCF to request that a UATI be assigned or re-assigned to the AT by the PCF. 2.5.2.1.1.1 Successful Operation

36 37 38 39

When the AN receives the UATIRequest message from the AT, the AN shall send an A14-UATI Request message to the PCF to request a UATI and start timer T14-UATI-Req. Refer to section 5.1.2.1, A14-UATI Request, for the format and content of this message.

2-7

A.S0007-A v3.0 HRPD IOS

1 2

May 2007

2.5.2.1.1.2

Failure Operation

If timer T14-UATI-Req expires, the AN may re-send the A14-UATI Request message to the PCF. 2.5.2.1.2 A14-UATI Assignment

3 4

The A14-UATI Assignment message is sent from the PCF to the AN to assign a UATI to the AT. 2.5.2.1.2.1 Successful Operation

5 6 7 8 9

When the PCF has an available UATI for a requesting AT, the PCF shall send an A14-UATI Assignment message to the AN to assign the UATI to the AT and start timer T14-UATI-Assign. The AN stops timer T14UATI-Req upon receipt of this message. Refer to section 5.1.2.2, A14-UATI Assignment, for the format and content of this message. 2.5.2.1.2.2 Failure Operation

10 11 12

If timer T14-UATI-Assign expires, the PCF may re-send the A14-UATI Assignment message to the AN. Otherwise the PCF should release the UATI. 2.5.2.1.3 A14-UATI Complete

13 14 15

The A14-UATI Complete message is sent from the AN to the PCF to notify the PCF that the UATI assignment procedure completed successfully. 2.5.2.1.3.1 Successful Operation

16 17 18 19 20

When the AN receives a UATIComplete message from the AT, the AN shall send an A14-UATI Complete message to notify the PCF that the UATI assignment completed successfully and start timer T14-UATI-Comp. The PCF stops timer T14-UATI-Assign upon receipt of this message. Refer to section 5.1.2.3, A14-UATI Complete, for the format and content of this message. 2.5.2.1.3.2 Failure Operation

21 22

If timer T14-UATI-Comp expires, the AN may re-send the A14-UATI Complete message to the PCF. 2.5.2.1.4 A14-UATI Complete Ack

23 24 25

The A14-UATI Complete Ack message is sent from the PCF to the AN to acknowledge the A14-UATI Complete message. 2.5.2.1.4.1 Successful Operation

26 27 28 29 30

When the PCF receives an A14-UATI Complete message from the AN, the PCF shall send an A14-UATI Complete Ack message to the AN to acknowledge that the UATI assignment procedure completed successfully. The AN stops timer T14-UATI-Comp. Refer to section 5.1.2.4, A14-UATI Complete Ack, for the format and content of this message. 2.5.2.1.4.2 None. 2.5.2.1.5 A14-UATI Assignment Failure Failure Operation

31 32

33 34 35

The A14-UATI Assignment Failure message is sent from the PCF to the AN to indicate failure to assign a UATI to the AT.

2-8

May 2007

1 2 3 4 5

A.S0007-A v3.0 HRPD IOS Successful Operation

2.5.2.1.5.1

When the PCF has no available UATI for the requesting AT, the PCF shall send an A14-UATI Assignment Failure message to the AN to indicate that a UATI is not assigned or re-assigned to the AT. The AN shall stop the timer T14-UATI-Req upon receipt of the A14-UATI Assignment Failure message. Refer to section 5.1.2.5, A14-UATI Assignment Failure, for the format and content of this message. 2.5.2.1.5.2 None. 2.5.2.2 General Updating Procedure Failure Operation

6 7

8 9 10

A14-General Update and A14-General Update Complete messages provide for mobility management. For call flows associated with the General Updating procedure, refer to sections 3.9.1 and 4.1.1. 2.5.2.2.1 A14-General Update

11 12 13

The A14-General Update message is sent from the AN to the PCF to update an AT's location information stored in the PCF. 2.5.2.2.1.1 Successful Operation

14 15 16 17 18 19 20 21

When the AN is required to update an AT's location information stored in the PCF and there is no need to send any other A14/A9 signaling (e.g., when the AN receives only a RouteUpdate message over the air interface), the AN shall send an A14-General Update message to the PCF and start timer Tgu14. When the AN performs the location update procedure with a dormant AT over the air interface, the AN shall send an A14-General Update message including the PANID, if received by the AN, to the PCF. Upon receipt of this message, the PCF performs an A10 connection establishment procedure, if required. Refer to section 5.1.2.6, A14-General Update, for the format and content of this message. 2.5.2.2.1.2 Failure Operation

22 23

If timer Tgu14 expires, the AN may re-send the A14-General Update message. 2.5.2.2.2 A14-General Update Complete

24 25 26

The A14-General Update Complete message is sent from the PCF to the AN to respond to the A14General Update message. 2.5.2.2.2.1 Successful Operation

27 28 29 30 31

When the PCF receives an A14-General Update message, the PCF shall update the AT's location information and send an A14-General Update Complete message to the AN. The AN shall stop timer Tgu14 upon receipt of this message. Refer to section 5.1.2.7, A14-General Update Complete, for the format and content of this message. 2.5.2.2.2.2 None. 2.5.2.3 Terminal Authentication Procedure Failure Operation

32 33

34 35 36 37

The PCF determines when the AN is required to perform terminal authentication, re-authentication or if authentication should be discontinued. For call flows associated with terminal authentication, refer to sections 3.1 and 4.1.2. For call flows associated with terminal re-authentication, refer to section 3.2. 2-9

A.S0007-A v3.0 HRPD IOS

1 2 3

May 2007

2.5.2.3.1

A14-Authentication Command

The A14-Authentication Command message is sent from the PCF to the AN to request that the AN start the terminal authentication procedure for an active AT. 2.5.2.3.1.1 Successful Operation

4 5 6 7

When the PCF decides that terminal authentication for an active AT is required, the PCF shall send an A14-Authentication Command message to the AN and start timer Tauthcom14. Refer to section 5.1.2.8, A14-Authentication Command, for the format and content of this message. 2.5.2.3.1.2 Failure Operation

8 9 10

If timer Tauthcom14 expires, the PCF may re-send the A14-Authentication Command message. If timer Tauthcom14 expires a second time, the PCF may initiate session clearing procedures. 2.5.2.3.2 A14-Authentication Request

11 12 13

The A14-Authentication Request message is sent from the AN to the PCF to establish the Ax interface for terminal authentication. 2.5.2.3.2.1 Successful Operation

14 15 16 17 18 19 20 21

When the AN is required by the PCF to perform terminal authentication, the AN prepares the terminal authentication and shall send an A14-Authentication Request message, including the Ax Traffic ID (IP Address and GRE key) used for the Ax interface on the AN side, to the PCF. If timer Tauthcom14 is running at the PCF, it is stopped upon receipt of the A14-Authentication Request message. The Ax Traffic ID is used in the GRE header of Ax traffic sent from the PCF. The AN shall start timer Tauthreq14 upon transmission of this message. Refer to section 5.1.2.9, A14-Authentication Request, for the format and content of this message. 2.5.2.3.2.2 Failure Operation

22 23 24 25 26

If timer Tauthreq14 expires, the AN may re-send the A14-Authentication Request message. If upon receipt of an A14-Authentication Request message the PCF decides that it is unable to perform the terminal authentication, the PCF shall send an A14-Authentication Completed message to the AN and start timer Tauthcomp14. Refer to section 2.5.2.3.4, A14-Authentication Completed. 2.5.2.3.3 A14-Authentication Response

27 28 29

The A14-Authentication Response message is sent from the PCF to the AN to establish the Ax interface for terminal authentication and is also used as the response to an A14-Authentication Request message. 2.5.2.3.3.1 Successful Operation

30 31 32 33 34 35

When the PCF receives an A14-Authentication Request message, the PCF shall send an A14-Authentication Response message including the Ax Traffic ID (IP Address and GRE key) used for the Ax interface on the PCF side, to the AN. The Ax Traffic ID is used in the GRE header of Ax traffic sent from the AN. The AN shall stop timer Tauthreq14 upon receipt of the A14-Authentication Response message. Refer to section 5.1.2.10, A14-Authentication Response, for the format and content of this message. 2.5.2.3.3.2 None Failure Operation

36 37

2-10

May 2007

1 2 3

A.S0007-A v3.0 HRPD IOS A14-Authentication Completed

2.5.2.3.4

The A14-Authentication Completed message is sent from the PCF to the AN after the terminal authentication procedure is finished. This message is also sent when the authentication is discontinued. 2.5.2.3.4.1 Successful Operation

4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

After the terminal authentication procedure performed between the AT and the PCF is finished, the PCF shall send an A14-Authentication Completed message with cause value set to `Authentication Succeeded', to the AN and start timer Tauthcomp14. If the authentication failed, the PCF may send an A14-Authentication Completed message with cause value set to `Authentication Failure', to the AN, and start timer Tauthcomp14. In this case, the AN shall release the resource for the Ax connection, stop timer Tauthreq14 and continue the operation. If the authentication failed and the PCF decides that the HRPD session should be released, the PCF shall send an A14-Session Release Command message with cause value set to `Authentication Failure', to the AN. In this case, the AN shall release the resource for the Ax connection and initiate HRPD session release procedure for the AT. Refer to section 2.5.2.4, for Session Release procedures. The A14-Authentication Completed message is sent when the PCF determines that the terminal authentication is to be discontinued (e.g., when the PCF is not able to access the AN-AAA) In this case, the PCF shall send an A14-Authentication Completed message and start timer Tauthcomp14. Refer to section 5.1.2.11, A14-Authentication Completed, for the format and content of this message. 2.5.2.3.4.2 Failure Operation

19 20 21

If timer Tauthcomp14 expires, the PCF may re-send the A14-Authentication Completed message. If the PCF does not re-send the message, the PCF shall release the resource for the Ax connection. 2.5.2.3.5 A14-Authentication Completed Ack

22 23 24

The A14-Authentication Completed Ack message is sent from the AN to the PCF to acknowledge the A14-Authentication Completed message. 2.5.2.3.5.1 Successful Operation

25 26 27 28 29

When the AN receives an A14-Authentication Completed message, the AN shall send an A14Authentication Completed Ack message to the PCF. The PCF shall release the resource for the Ax connection and stop timer Tauthcomp14. Refer to section 5.1.2.12, A14-Authentication Completed Ack, for the format and content of this message. 2.5.2.3.5.2 None. 2.5.2.3.6 A14-Authentication Failure Failure Operation

30 31

32 33 34

The A14-Authentication Failure message is sent from the AN to the PCF to indicate a failure condition occurred during the terminal authentication procedure. 2.5.2.3.6.1 Successful Operation

35 36 37 38

If the AN is unable to start or continue the terminal authentication, the AN shall send an A14Authentication Failure message to the PCF and start timer Tauthfail14. Refer to section 5.1.2.13, A14-Authentication Failure, for the format and content of this message.

2-11

A.S0007-A v3.0 HRPD IOS

1 2

May 2007

2.5.2.3.6.2

Failure Operation

If timer Tauthfail14 expires, the AN may re-send the A14-Authentication Failure message. 2.5.2.3.7 A14-Authentication Failure Ack

3 4 5

The A14-Authentication Failure Ack message is sent from the PCF to the AN to acknowledge the A14Authentication Failure message. 2.5.2.3.7.1 Successful Operation

6 7 8 9 10 11 12

When the PCF receives an A14-Authentication Failure message, the PCF shall discontinue the terminal authentication procedure, send an A14-Authentication Failure Ack message to the AN, stop timer Tauthcmd14 if it is running, and release the Ax connection if it exists. Upon receipt of the A14Authentication Failure Ack message, the AN shall stop timer Tauthfail14, release the Ax connection if it exists and stop timer Tauthreq14 if it is running. Refer to section 5.1.2.14, A14-Authentication Failure Ack, for the format and content of this message. 2.5.2.3.7.2 None. 2.5.2.4 Session Release Failure Operation

13 14

15 16 17

The HRPD session may be released by the AT, AN or the PCF. For call flows associated with session release, refer to section 3.5. 2.5.2.4.1 A14-Session Release Command

18 19 20

The A14-Session Release Command message is sent from the PCF to the AN to request the AN to initiate the procedure for releasing the HRPD session. 2.5.2.4.1.1 Successful Operation

21 22 23 24 25

When the PCF decides to release the HRPD session, the PCF shall send an A14-Session Release Command message to the AN and start timer Trelcom14. Upon receipt of this message, the AN stops timer Tauthreq14 if it is running. Refer to section 5.1.2.15, A14-Session Release Command, for the format and content of this message. 2.5.2.4.1.2 Failure Operation

26 27

If timer Trelcom14 expires, the PCF may re-send the A14-Session Release Command message. 2.5.2.4.2 A14-Session Release

28 29 30

The A14-Session Release message is sent from the AN to the PCF to request the PCF to release the associated dedicated resource. 2.5.2.4.2.1 Successful Operation

31 32 33 34 35

After the AN closes the HRPD session, the AN sends an A14-Session Release message to the PCF to request the PCF to release the associated dedicated resource and the associated A10 connection. The AN starts timer Trel14. The PCF shall stop timer Trelcom14, if it is running, upon receipt of this message. Refer to section 5.1.2.16, A14-Session Release, for the format and content of this message.

2-12

May 2007

1 2

A.S0007-A v3.0 HRPD IOS Failure Operation

2.5.2.4.2.2

If timer Trel14 expires, the AN may re-send the A14-Session Release message. 2.5.2.4.3 A14-Session Release Complete

3 4 5

The A14-Session Release Complete message is sent from the PCF to the AN to notify the AN that session release is completed. 2.5.2.4.3.1 Successful Operation

6 7 8 9

When the PCF finishes releasing the associated dedicated resource and the associated A10 connection, the PCF sends an A14-Session Release Complete message to the AN. The AN stops timer Trel14. Refer to section 5.1.2.17, A14-Session Release Complete, for the format and content of this message. 2.5.2.4.3.2 None 2.5.2.5 Session Information Transfer Procedure Failure Operation

10 11

12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

When the session information is required at the AN to process a call, session information stored in the PCF is transferred to the AN by using either following scenario. · · The PCF includes the session information in an A9-Connect-A8 or an A9-Release-A8 Complete message when the AN establishes the A8 connection. The PCF includes the session information in an A14-Paging Request message and/or an A14-Paging Response Ack message when the paging procedure is performed.

When the session information is updated at the AN during an active HRPD session, the updated session information is transferred to the PCF by using either following scenario. · · The AN includes updated session information in an A9-Release-A8 message when the AN disconnects the A8 connection for the AT. The AN includes updated session information in an A14-Session Information Update message when the AN decides that updated session information should be transferred, during an active HRPD session.

For call flows associated with session information transfer and update, refer to sections 3.1 and 3.8.2. 2.5.2.5.1 A14-Session Information Update

27 28 29

The A14-Session Information Update message is sent from the AN to the PCF for the PCF to update the session information of an AT. 2.5.2.5.1.1 Successful Operation

30 31 32 33

When the AN decides that updated session information should be transferred to the PCF, the AN shall send an A14-Session Information Update message to the PCF and start timer Tsu14. Refer to section 5.1.2.18, A14-Session Information Update, for the format and content of this message. 2.5.2.5.1.2 Failure Operation

34 35

If timer Tsu14 expires, the AN may re-send the A14-Session Information Update message.

2-13

A.S0007-A v3.0 HRPD IOS

1 2 3

May 2007

2.5.2.5.2

A14-Session Information Update Ack

The A14-Session Information Update Ack message is sent from the PCF to the AN to acknowledge the A14-Session Information Update message. 2.5.2.5.2.1 Successful Operation

4 5 6 7 8 9

When the PCF receives the A14-Session Information Update message, the PCF shall update the session information stored in the PCF and send an A14-Session Information Update Ack message to the AN. The AN shall stop timer Tsu14 upon receipt of this message. Refer to section 5.1.2.19, A14-Session Information Update Ack, for the format and content of this message. 2.5.2.5.2.2 None. 2.5.2.6 Paging Procedure Failure Operation

10 11

12 13 14 15 16 17

The paging procedure is used to initiate the establishment of an HRPD air interface connection between an AT and an AN. This procedure may also be used to perform the following. · To transmit packet data from a PCF to a dormant AT. · To perform terminal authentication of a dormant AT. For call flows associated with the A14 paging procedure, refer to sections 3.2.1, 3.2.2 and 3.3.1. 2.5.2.6.1 A14-Paging Request

18 19 20

The A14-Paging Request message is sent from the PCF to an AN to request that the AN start the paging procedure. 2.5.2.6.1.1 Successful Operation

21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

When the PCF receives packet data for a dormant AT, the PCF buffers the received data and sends an A14-Paging Request message, with the Data Ready Indicator bit in the A14 Indicators information element (IE) set to `1', to the AN. When the PCF decides that terminal authentication for a dormant AT should be performed, the PCF shall send an A14-Paging Request message, with the Authentication Required bit in the A14 Indicators IE set to `1', to the AN. If the PCF receives packet data for the AT, and the PCF chooses to perform terminal authentication, the PCF sets the Data Ready Indicator and Authentication Required bits in the A14 Indicators IE to `1' in the A14-Paging Request message. In this case, the AN shall proceed with the terminal authentication first and then establish an A8 connection after terminal authentication is successfully completed. If the PCF requires an A14-Paging Request Ack message, the PCF shall set the Paging Type Indicator in the A14 Indicators IE to `0' and start timer Tpreq14. If the PCF does not require an A14-Paging Request Ack message, the PCF shall set the Paging Type Indicator in the A14 Indicators IE to `1' and start timer Tpage14. In this case, the AN starts the paging procedure in accordance with [10] upon receipt of the A14-Paging Request message. Refer to section 5.1.2.20, A14-Paging Request, for the format and content of this message. 2.5.2.6.1.2 Failure Operation

38 39 40

If timer Tpreq14 expires, the PCF may re-send the A14-Paging Request message. If timer Tpage14 expires, the PCF may re-send the A14-Paging Request message. 2-14

May 2007

1 2 3

A.S0007-A v3.0 HRPD IOS A14-Paging Request Ack

2.5.2.6.2

The A14-Paging Request Ack message is sent from the AN to the PCF in response to an A14-Paging Request message sent from the PCF, if the Paging Type Indicator in the A14 Indicators IE is set to `0'. 2.5.2.6.2.1 Successful Operation

4 5 6 7 8 9 10 11 12 13

When the AN receives an A14-Paging Request message with the Paging Type Indicator in the A14 Indicators IE set to `0', the AN shall send an A14-Paging Request Ack message to the PCF and start the paging procedure in accordance with [10]. When the PCF receives the A14-Paging Request Ack message, the PCF shall stop timer Tpreq14. The PCF may have an internal timer, which is started when the PCF receives the A14-Paging Request Ack message, and is stopped when the PCF receives the A9-Setup-A8 message, to detect paging failure. Upon expiration of this internal timer, the PCF may re-send the A14-Paging Request message a configurable number of times. Refer to section 5.1.2.21, A14-Paging Request Ack , for the format and content of this message. 2.5.2.6.2.2 None. 2.5.2.6.3 A14-Paging Response Failure Operation

14 15

16 17 18

The A14-Paging Response message is sent from the AN to the PCF to indicate that the AT has responded to a page. 2.5.2.6.3.1 Successful Operation

19 20 21 22 23 24 25

If the AN receives an A14-Paging Request message with the Paging Type Indicator in the A14 Indicators IE set to `1', after the AN receives a response from the AT, the AN shall send an A14-Paging Response message to the PCF and start timer Tprsp14. Note that if inter-AN paging is used, the AN that sends the A14-Paging Response message may not be the same AN that received the A14-Paging Request message. When the PCF receives the A14-Paging Response message, the PCF shall stops timer Tpage14. Refer to section 5.1.2.22, A14-Paging Response, for the format and content of this message. 2.5.2.6.3.2 Failure Operation

26 27

If timer Tprsp14 expires, the AN may re-send the A14-Paging Response message. 2.5.2.6.4 A14-Paging Response Ack

28 29 30

The A14-Paging Response Ack message is sent from the PCF to an AN in response to the A14-Paging Response message, if the Paging Type Indicator in the A14 Indicators IE is set to `1'. 2.5.2.6.4.1 Successful Operation

31 32 33 34 35

When the PCF receives an A14-Paging Response message, the PCF sends an A14-Paging Response Ack message to the AN and includes a Session State Information Record in this message. When the AN receives the A14-Paging Response Ack message, the AN shall stop timer Tprsp14. Refer to section 5.1.2.23, A14-Paging Response Ack, for the format and content of this message. 2.5.2.6.4.2 None. Failure Operation

36 37

2-15

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5

May 2007

2.5.2.7

Session Keep Alive Procedure

The PCF may perform the session keep alive procedure to identify the session being kept alive and to maintain the current session when the AT is in dormant state. The session keep alive procedure does not occur when the AT is in the active state. For a call flow associated with the Session Keep Alive procedure, refer to section 3.9.2. 2.5.2.7.1 A14-Keep Alive Request

6 7

The A14-Keep Alive Request message is sent from the PCF to the AN to check if the AT is alive. 2.5.2.7.1.1 Successful Operation

8 9 10 11 12

When the PCF decides to check the AT status, the PCF shall send an A14-Keep Alive Request message to the AN and start timer Tkareq14. Upon receipt of this message, the AN conducts keep alive procedures with the AT; refer to [10]. Refer to section 5.1.2.24, A14-Keep Alive Request, for the format and content of this message. 2.5.2.7.1.2 Failure Operation

13 14

If timer Tkareq14 expires, the PCF may re-send the A14-Keep Alive Request message. 2.5.2.7.2 A14-Keep Alive Request Ack

15 16 17

The A14-Keep Alive Request Ack message is sent from the AN to the PCF to acknowledge the A14Keep Alive Request message. 2.5.2.7.2.1 Successful Operation

18 19 20 21

When the AN receives the A14-Keep Alive Request message, the AN shall send an A14-Keep Alive Request Ack message to the PCF. The PCF shall stop timer Tkareq14 upon receipt of the message. Refer to section 5.1.2.25, A14-Keep Alive Request Ack, for the format and content of this message. 2.5.2.7.2.2 None. Failure Operation

22 23 24

2-16

May 2007

A.S0007-A v3.0 HRPD IOS

1

2.6

A15 (AN - AN) Interface

2 3

The A15 interface is used for sending paging request messages from the AN that manages the registered sector to the ANs that send paging messages over the air. This interface is used for inter AN paging. 2.6.1 A15 Interface Network/Transport Protocol Specification

4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

Signaling over the A15 interface requires a reliable transport protocol. To realize reliable transport, the underlying transport guarantees low packet loss. However, the selection of the underlying transport is left to the discretion of the operators and manufacturers. The signaling protocol stack available to operators and manufacturers, for the A15 interface is: IOS Application TCP/UDP IP Link Layer Physical Layer When TCP is used as the transport, an AN shall use the following well-known TCP port number for receiving/sending message over the A15 interface. · A15 (AN-to-AN) 3598/tcp - This is the well-known TCP port number to be used for signaling interconnection to another AN. When UDP is used as the transport, an AN shall use the following well-known UDP port number for receiving/sending message over the A15 interface. · A15 (AN-to-AN) 3598/udp - This is the well-known UDP port number to be used for signaling interconnection to another AN. 2.6.2 A15 Interface Procedures

22 23

This section describes the procedures for messages carried on the A15 interface. 2.6.2.1 Paging Procedure

24 25 26

In the paging procedure using A15 interface messaging, the AN receiving an A14-Paging Request message acts as the source AN. For call flows associated with A15 paging, refer to section 3.3.1. 2.6.2.1.1 A15-Paging Request

27 28 29

The A15-Paging Request message is sent from the source AN which receives the A14-Paging Request message to any other AN involved in the paging procedure. 2.6.2.1.1.1 Successful Operation

30 31 32 33 34 35 36

When the source AN receives an A14-Paging Request message from the PCF, with the A15 Paging Inhibited Indicator bit set to `0', if the source AN decides that inter-AN paging is required, the source AN sends an A15-Paging Request message to the target ANs determined to be involved in the paging procedure. The source AN shall start timer Tpreq15. If the source AN receives a paging response from the AT, the source AN shall stop timer Tpreq15. Refer to section 5.1.3.1, A15-Paging Request, for the format and content of this message. 2.6.2.1.1.2 Failure Operation

37 38 39

If timer Tpreq15 expires, the source AN may start the paging procedure again. If the source AN does not continue the paging procedure, the source AN shall assume that the paging procedure failed. 2-17

A.S0007-A v3.0 HRPD IOS

1 2 3

May 2007

2.6.2.1.2

A15-Paging Response

The A15-Paging Response message is sent from the target AN to the source AN when the target AN receives a paging response from the AT. 2.6.2.1.2.1 Successful Operation

4 5 6 7 8 9

Upon receipt of a paging response over the air interface from the AT, the target AN shall send an A15Paging Response message to the source AN and start timer Tprsp15. The target AN shall establish an A8 connection for the AT. The source AN shall stop timer Tpreq15 upon receipt of the A15-Paging Response message. Refer to section 5.1.3.2, A15-Paging Response, for the format and content of this message. 2.6.2.1.2.2 Failure Operation

10 11

If timer Tprsp15 expires, the target AN may re-send the A15-Paging Response message to the source AN. 2.6.2.1.3 A15-Paging Response Ack

12 13 14

The A15-Paging Response Ack message is sent from the source AN to the target AN to acknowledge the receipt of an A15-Paging Response message. 2.6.2.1.3.1 Successful Operation

15 16 17 18 19

When the source AN receives an A15-Paging Response message, the source AN shall send an A15Paging Response Ack message to the target AN. When the target AN receives the A15-Paging Response Ack message, the target AN shall stop timer Tprsp15. Refer to section 5.1.3.3, A15-Paging Response Ack, for the format and content of this message. 2.6.2.1.3.2 None. Failure Operation

20 21

22 23 24

2.7

Ax (AN - PCF) Interface

The Ax interface is used for carrying data relating to terminal authentication, which is transmitted in the access stream over the air interface. 2.7.1 Ax Interface Network/Transport Protocol Specification

25 26 27 28 29 30 31 32 33 34 35 36

The Ax interface is a user data interface. The upper layer of the Ax interface is the Generic Routing Encapsulation (GRE) protocol as defined in [21]. Refer to section 5.4.7 of [11] for the usage of the GRE protocol. The protocol stack for the Ax interface is shown as follows. Access Stream Data GRE IP Link Layer Physical Layer The Protocol Type field of the GRE header shall be set to 88 81H (unstructured byte stream) for the Ax interface.

2-18

May 2007

1

A.S0007-A v3.0 HRPD IOS

3 HRPD IOS Call Flows

This section describes the call flows associated with an HRPD AT. While specific air interface messages may be identified in the HRPD IOS call flows, they are provided only for AN trigger references. Refer to [10] for the definitions and formats of these messages.

2 3 4

5

3.1

AT Originates HRPD Session

6

This section describes the call flows associated with an AT call origination in the AN. 3.1.1 AT Originates HRPD Session - Successful Terminal Authentication

7 8

This scenario describes the call flow for a successfully authenticated AT call origination in the AN.

AT UATIRequest AN PCF AN AAA PDSN time a

T14-UATI-Req

UATIAssignment UATIComplete

A14-UATI Request A14-UATI Assignment

b c d e

T14-UATI-Assign T14-UATI-Comp

A14-UATI Complete A14-UATI Complete Ack

f g h

ConnectionRequest

TA8-setup

A9-Setup-A8 (DRI=1) A9-Release-A8 Complete (Authentication required, Session Information (Default)) j

i

TCH Establishment

k

Session Negotiation Connection Release

l

m

Tsu14

ConnectionRequest TCH Establishment

A14-Session Info Update A14-Session Info Update Ack

n o p q

Tauthreq14

Location Update Procedure

A14-Authentication Request A14-Authentication Response

r s t optional

AT or AN indicates ready to exchange data on access stream PPP and LCP Negotiation

u

v

CHAP Challenge - Response

9 10

w

Figure 3.1.1-1 Initial AT Origination with HRPD Session Establishment and Key Exchange

3-1

A.S0007-A v3.0 HRPD IOS

AT AN PCF AN AAA

May 2007

PDSN time

A12 Access-Request A12 Access-Accept CHAP - Authentication Success A14-Authentication Completed (Authentication Succeded) A14-Authentication Completed Ack AT ready to exchange data on service stream A9-Setup-A8 (DRI=1)

x y z aa

Tauthcomp14

bb cc dd

TA8-setup

A9-Connect-A8

Tregreq

A11-Registration Request A11-Registration Reply

ee ff gg hh ii

Establishing PPP connection Transmitting packet data

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

Figure 3.1.1-1 Initial AT Origination with HRPD Session Establishment and Key Exchange Continued a. The AT sends a UATIRequest message to request that a UATI be assigned to it. b. The AN sends an A14-UATI Request message to the PCF to request that the PCF assign a UATI for the AT. The AN starts timer T14-UATI-Req. c. Upon receipt of the A14-UATI Request message, the PCF assigns a UATI for the AT from its UATI pool, sends an A14-UATI Assignment message including assigned UATI and starts timer T14-UATIAssign. The AN stops timer T14-UATI-Req upon receipt of this message. d. The AN sends a UATIAssignment message to assign a UATI to the AT. e. The AT sends a UATIComplete message to notify the AN that it has received the UATIAssignment message. f. Upon receipt of the UATIComplete message from the AT, the AN sends an A14-UATI Complete message to the PCF to notify the PCF that UATI assignment completed successfully. The AN starts timer T14-UATI-Comp. The PCF stops timer T14-UATI-Assign upon receipt of the A14-UATI Complete message.

g. The PCF sends an A14-UATI Complete Ack message to the AN as an acknowledgment. The AN stops timer T14-UATI-Comp. h. The AT sends a ConnectionRequest message to the AN to request TCH establishment. i. j. The AN sends an A9-Setup-A8 message to the PCF with Data Ready Indicator (DRI) set to `1', to establish the A8 connection. The AN starts timer TA8-setup. Upon receipt of the A9-Setup-A8 message, the PCF checks the status of the AT, decides that the AT should be authenticated, and then sends an A9-Release-A8 Complete message to the AN containing session information and requesting terminal authentication. In this case, default configurations are used for the session information. The AN stops timer TA8-setup upon receipt of this message.

k. The AT and the AN establish a TCH. l. The AT and the AN negotiate the required session. m. After the session negotiation between the AT and the AN, the initial connection is released. 3-2

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45

A.S0007-A v3.0 HRPD IOS

n. The AN sends an A14-Session Information Update message to the PCF to update the negotiated session information at the PCF. The AN starts timer Tsu14. o. The PCF responds with an A14-Session Information Update Ack message to acknowledge receipt of the A14-Session Information Update message from the AN. The AN stops timer Tsu14 upon receipt of this message. p. The AT sends a ConnectionRequest message to the AN. q. The AT and the AN establish a TCH. r. s. The AN sends an A14-Authentication Request message to the PCF to indicate the resource (i.e. IP address and GRE key) for the authentication at the AN. The AN starts timer Tauthreq14. The PCF sends an A14-Authentication Response message to the AN to indicate the resource (i.e. IP address and GRE key) for the authentication at the PCF. The AN stops timer Tauthreq14 upon receipt of the A14-Authentication Response message. If the AN supports the Location Update procedure, the AN updates the ANID in the AT using the Location Update procedure. The AN may also retrieve the PANID from the AT if necessary. This step may occur any time after step q. Refer to section 4.1.1 for additional information.

t.

u. The AT or the AN indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol for the default packet application bound to the RAN is in the open state). Note that this may occur at any time after step `q'. v. The AT and the PCF initiate Point-to-Point Protocol (PPP) and LCP negotiations for terminal authentication. Refer to [19]. w. The PCF generates a random challenge and sends it to the AT in a CHAP Challenge message in accordance with [23]. x. When the PCF receives the CHAP response message from the AT, it sends an Access-Request message on the A12 interface to the AN-AAA which acts as a RADIUS server in accordance with [25]. y. The AN-AAA looks up a password based on the User-name attribute in the Access-Request message and if the terminal authentication passes (as specified in [23] and [25]), the AN-AAA sends an Access-Accept message on the A12 interface in accordance with [25] (RADIUS). The Access-Accept message contains a RADIUS attribute with Type set to 20 (Callback-Id), which is set to the MN ID of the AT. Refer to section 2.3.2, AN-AAA Support. z. The PCF returns an indication of CHAP terminal authentication success to the AT. Refer to [23]. aa. The PCF sends an A14-Authentication Completed message indicating that the authentication completed successfully and starts timer Tauthcomp14. bb. The AN sends an A14-Authentication Completed Ack message to the PCF. The PCF stops timer Tauthcomp14 upon receipt of the message. cc. The AT indicates that it is ready to exchange data on the service stream (e.g., the flow control protocol for the default packet application bound to the packet data network is in the open state). Note that this step may occur anytime after step `u'. dd. The AN sends an A9-Setup-A8 message to the PCF with Data Ready Indicator (DRI) set to `1' to establish the A8-Connection and starts timer TA8-setup. ee. The PCF recognizes that no A10 connection associated with the AT is available and selects a PDSN using the selection algorithm defined in [11]. The PCF sends an A11-Registration Request message to the PDSN. The PCF starts Tregreq. ff. The A11-Registration Request is validated and the PDSN accepts the connection by returning an A11-Registration Reply with an accept indication and Lifetime set to the configured Trp value. If the 3-3

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10

May 2007

PDSN has data to send, it includes the Data Available Indicator (DAI) within the CVSE. The A10 connection binding information at the PDSN is updated to point to the PCF. The PCF stops timer TA8-setup. gg. The PCF sends an A9-Connect-A8 message to the AN. The AN stops timer TA8-setup upon receipt of the message. hh. PPP connection establishment procedure is performed between the AT and the PDSN, according to [9]. ii. At this point the connection is established and packet data can flow between the AT and the PDSN.

3-4

May 2007

A.S0007-A v3.0 HRPD IOS

1 2 3

3.1.2

AT Originates HRPD Session - Unsuccessful Terminal Authentication

This scenario describes the call flow for an unsuccessful AT call origination in the AN, due to terminal authentication failure.

AT UATIRequest AN PCF AN AAA PDSN time a

T14-UATI-Req

UATIAssignment UATIComplete

A14-UATI Request A14-UATI Assignment

b c d e

T14-UATI-Assign T14-UATI-Comp

A14-UATI Complete A14-UATI Complete Ack

f g h

ConnectionRequest

TA8-setup

A9-Setup-A8 (DRI=1) A9-Release-A8 Complete (Authentication required, Session Information (Default)) j

i

TCH Establishment

k

Session Negotiation Connection Release

l

m

Tsu14

ConnectionRequest TCH Establishment

A14-Session Info Update A14-Session Info Update Ack

n o p q

Tauthreq14

AT or AN indicates ready to exchange data on access stream

A14-Authentication Request A14-Authentication Response

r s t

PPP and LCP Negotiation

u

CHAP Challenge - Response A12 Access Request A12 Access Reject CHAP - Authentication Failure A14-Session Release Command (Authentication Failure) SessionClose SessionClose

v w x y z aa

Trelcom14 Trel14

A14-Session Release A14-Session Release Complete

bb cc dd

4 5

Figure 3.1.2-1 Initial AT Origination - Unsuccessful Terminal Authentication a. The AT sends a UATIRequest message to request that a UATI be assigned to it. 3-5

6

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

May 2007

b. The AN sends an A14-UATI Request message to the PCF to request the PCF assign a UATI for the AT. The AN starts timer T14-UATI-Req. c. Upon receipt of the A14-UATI Request message, the PCF assigns a UATI for the AT from its UATI pool, sends an A14-UATI Assignment message including assigned UATI and starts timer T14-UATIAssign. The AN stops timer the T14-UATI-Req upon receipt of this message. d. The AN sends a UATIAssignment message to assign a UATI to the AT. e. The AT sends a UATIComplete message to notify the AN that it has received the UATI-Assignment message. f. Upon receipt of the UATIComplete message from the AT, the AN sends an A14-UATI Complete message to the PCF to notify the PCF that UATI assignment completed successfully. The AN starts timer T14-UATI-Comp. The PCF stops timer T14-UATI-Assign upon receipt of the A14-UATI Complete message.

g. The PCF sends an A14-UATI Complete Ack message to the AN as an acknowledgment. The AN stops timer T14-UATI-Comp. h. The AT sends a ConnectionRequest message to the AN to request TCH establishment. i. j. The AN sends an A9-Setup-A8 message to the PCF with Data Ready Indicator (DRI) set to `1', to establish the A8 connection. The AN starts timer TA8-setup. Upon receipt of the A9-Setup-A8 message, the PCF checks the status of the AT and sends an A9Release-A8 Complete message requesting the preparation of the terminal authentication, because the PCF decides that the AT should be authenticated in this case. Simultaneously, the PCF sends session information to the AN. In this case, default configurations are used for the session information. The AN stops timer TA8-setup.

k. The AT and the AN establish a TCH. l. The AT and the AN negotiate the required session. m. After the session negotiation between the AT and the AN, the initial connection is released. n. The AN sends an A14-Session Information Update message to the PCF to update the negotiated session information at the PCF. The AN starts timer Tsu14. o. The PCF responds with an A14-Session Information Update Ack message to acknowledge the A14Session Information Update message from the AN. The AN stops timer Tsu14 upon receipt of this message. p. The AT sends a ConnectionRequest to the AN. q. The AT and the AN establish a TCH. r. s. The AN sends an A14-Authentication Request message to the PCF to indicate the resource for the authentication at the AN. The AN starts timer Tauthreq14. The PCF sends an A14-Authentication Response message to the AN to indicate the resource for the authentication at the PCF. The AN stops timer Tauthreq14 upon receipt of the A14-Authentication Response message. The AT or the AN indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol for the default packet application bound to the RAN is in the open state). Note that this may occur at any time after step `q'.

t.

u. The AT and the PCF initiate Point-to-Point Protocol (PPP) and LCP negotiations for terminal authentication. Refer to [19].

3-6

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

A.S0007-A v3.0 HRPD IOS

v. The PCF generates a random challenge and sends it to the AT in a CHAP Challenge message in accordance with [23]. w. When the PCF receives the CHAP response message from the AT, it sends an Access-Request message on the A12 interface to the AN-AAA which acts as a RADIUS server in accordance with [25]. x. The AN-AAA looks up a password based on the User-name attribute in the Access-Request message and if the terminal authentication fails (as specified in [23] and [25]), the AN-AAA sends an AccessReject message on the A12 interface in accordance with [25] (RADIUS). Note: For ANs that perform terminal authentication, the network requires that no use of a dedicated resource, such as access to a PDSN, be allowed if authentication fails. y. The PCF returns an indication of CHAP terminal authentication failure to the AT. Refer to [23]. z. The PCF sends an A14-Session Release Command message indicating that the authentication is failed and starts timer Trelcom14. aa. The AN sends a SessionClose message to the AT to close the HRPD session. bb. The AT responds with a SessionClose message. cc. The AN sends an A14-Session Release message to the PCF and starts timer Trel14. The PCF stops timer Trelcom14 upon receipt of this message. dd. The PCF sends an A14-Session Release Complete message to the AN. The AN stops timer Trel14 upon receipt of this message.

3-7

A.S0007-A v3.0 HRPD IOS

May 2007

1

3.2

Re-authentication

2

This section describes the call flows associated with the re-authentication of an AT. 3.2.1 Re-authentication of an AT in Dormant State without Paging Response

3 4 5 6

This scenario describes the call flow associated with re-authentication of a dormant AT when the Paging Type Indicator is set to `0' (Paging Response is not required). It is assumed that the AT has already established an HRPD session.

AT AN PCF AN AAA time

A14-Paging Request (Authentication Required) A14-Paging Request Ack Page Connection Establishment

a

Tpreq14

b c d

Tauthreq14

A14-Authentication Request A14-Authentication Response

e f g

AT or AN indicates ready to exchange data on access stream

PPP and LCP Negotiation

h

CHAP Challenge - Response A12 Access-Request A12 Access-Accept CHAP - Authentication Success A14-Authentication Completed

i j k l m

Tauthcomp14

A14-Authentication Completed Ack Connection Release n o

7 8

Figure 3.2.1-1 Re-authentication of an AT in Dormant State without Paging Response a. The PCF determines that a re-authentication of an AT is required and sends an A14-Paging Request message, to the AN with the Authentication Required Indicator set to `1' and the Paging Type Indicator set to `0'. The PCF starts timer Tpreq14. b. The AN responds with an A14-Paging Request Ack message in response to the A14-Paging Request message. Upon receipt of this message, the PCF stops timer Tpreq14. c. The AN sends a Page message to the AT. d. The AN and the AT establish the connection. e. The AN sends an A14-Authentication Request message to the PCF to indicate the resource (i.e. IP address and GRE key) for the authentication at the AN. The AN starts timer Tauthreq14.

9 10 11 12 13 14 15 16 17

3-8

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

A.S0007-A v3.0 HRPD IOS

f.

The PCF sends an A14-Authentication Response message to the AN to indicate the resource (i.e. IP address and GRE key) for the authentication at the PCF. The AN stops timer Tauthreq14 upon receipt of the A14-Authentication Response message.

g. The AT or the AN indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol for the default packet application bound to the RAN is in the open state). Note that this may occur at any time after step `d'. h. The AT and the PCF initiate PPP and LCP negotiations for terminal authentication. Refer to [19]. This step is omitted when the PCF and the AT keep the PPP connection after initial terminal authentication. i. j. The PCF generates a random challenge and sends it to the AT in a CHAP Challenge message in accordance with [23]. When the PCF receives the CHAP response message from the AT, it sends an Access-Request message on the A12 interface to the AN-AAA which acts as a RADIUS server in accordance with [25].

k. The AN-AAA looks up a password based on the User-name attribute in the Access-Request message and if the terminal authentication passes (as specified in [23] and [25]), the AN-AAA sends an Access-Accept message on the A12 interface in accordance with [25] (RADIUS). The Access-Accept message contains a RADIUS attribute with Type set to 20 (Callback-Id), which is set to the MN ID of the AT. Refer to section 2.3.2, AN-AAA Support. l. The PCF returns an indication of CHAP terminal authentication success to the AT. Refer to [23]. m. The PCF sends an A14-Authentication Completed message indicating that the authentication completed successfully and starts timer Tauthcomp14. n. The AN sends an A14-Authentication Completed Ack message to the PCF. The PCF stops timer Tauthcomp14 upon receipt of the message. o. The AN initiates HRPD connection tear-down. Refer to [10], section 6, Connection Layer.

3-9

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3 4

3.2.2

Re-authentication of an AT in Dormant State with Paging Response

This scenario describes the call flow associated with re-authentication of a dormant AT when the Paging Type Indicator is set to `1' (Paging Response is required). It is assumed that the AT has already established an HRPD session.

AT AN A14-Paging Request (Authentication Required) Page Connection Establishment PCF AN AAA time

a

Tpage14

A14-Paging Response A14-Paging Response Ack A14-Authentication Request A14-Authentication Response

b c d e f g h

Tprsp14

Tauthreq14

AT or AN indicates ready to exchange data on access stream

PPP and LCP Negotiation

i

CHAP Challenge - Response A12 Access-Request A12 Access-Accept CHAP - Authentication Success A14-Authentication Completed

j k l m n

Tauthcomp14

A14-Authentication Completed Ack Connection Release o p

5 6

Figure 3.2.2-1 Re-authentication of an AT in Dormant State with Paging Response a. The PCF determines that a re-authentication of an AT is required and sends an A14-Paging Request message, to the AN with the Authentication Required Indicator set to `1' and the Paging Type Indicator set to `1'. The PCF starts timer Tpage14. b. The AN sends a Page message to the AT. c. The AN and the AT establish the connection. d. The AN sends an A14-Paging Response message to the PCF after connection establishment and starts timer Tprsp14. The PCF stops timer Tpage14 upon receipt of this message. e. The PCF sends an A14-Paging Response Ack message to the AN in response to the A14-Paging Response message. The AN stops timer Tprsp14 upon receipt of the message. f. The AN sends an A14-Authentication Request message to the PCF to indicate the resource (i.e. IP address and GRE key) for the authentication at the AN. The AN starts timer Tauthreq14.

7 8 9 10 11 12 13 14 15 16 17

3-10

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

A.S0007-A v3.0 HRPD IOS

g. The PCF sends an A14-Authentication Response message to the AN to indicate the resource (i.e. IP address and GRE key) for the authentication at the PCF. The AN stops timer Tauthreq14 upon receipt of the A14-Authentication Response message. h. The AT or the AN indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol for the default packet application bound to the RAN is in the open state). Note that this may occur at any time after step `c'. i. The AT and the PCF initiate PPP and LCP negotiations for terminal authentication. Refer to [19]. This step is omitted when the PCF and the AT keep the PPP connection after initial terminal authentication. The PCF generates a random challenge and sends it to the AT in a CHAP Challenge message in accordance with [23].

j.

k. When the PCF receives the CHAP response message from the AT it send an Access-Request message on the A12 interface to the AN-AAA which acts as a RADIUS server in accordance with [25]. l. The AN-AAA looks up a password based on the User-name attribute in the Access-Request message and if the terminal authentication passes (as specified in [23] and [25]), the AN-AAA sends an Access-Accept message on the A12 interface in accordance with [25] (RADIUS). The Access-Accept message contains a RADIUS attribute with Type set to 20 (Callback-Id), which is set to the MN ID of the AT. Refer to section 2.3.2, AN-AAA Support.

m. The PCF returns an indication of CHAP terminal authentication success to the AT. Refer to [23]. n. The PCF sends an A14-Authentication Completed message indicating that the authentication completed successfully and starts timer Tauthcomp14. o. The AN sends an A14-Authentication Completed Ack message to the PCF. The PCF stops timer Tauthcomp14 upon receipt of the message. p. The AN initiates HRPD connection tear-down. Refer to [10], section 6, Connection Layer.

3-11

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3

3.2.3

Re-authentication of an AT in Active State

This scenario describes the call flow associated with re-authentication of an active AT. It is assumed that the AT has already established an HRPD session.

AT AN PCF AN AAA time

A14-Authentication Command A14-Authentication Request

Tauthcom14

a b

Tauthreq14

A14-Authentication Response c

AT ready to exchange data on access stream

d e f A12 Access-Request A12 Access-Accept g h i j

PPP and LCP Negotiation CHAP Challenge - Response

CHAP - Authentication Success A14-Authentication Completed

Tauthcomp14

A14-Authentication Completed Ack AT ready to exchange data on service stream k l

4 5

Figure 3.2.3-1 Re-authentication of an AT in Active State a. The PCF determines that re-authentication of an AT is required and sends an A14-Authentication Command message to the AN to request the AN to prepare for terminal authentication. The PCF starts timer Tauthcom14. b. The AN sends an A14-Authentication Request message to the PCF to request setup of the Ax connection to be used for terminal authentication. The AN starts timer Tauthreq14. Upon receipt of the A14-Authentication Request message the PCF stops timer Tauthcom14. c. The PCF sends an A14-Authentication Response message to the AN to establish the Ax connection to be used for terminal authentication. The AN stops timer Tauthreq14 upon receipt of the A14Authentication Response message. d. Upon receipt of the A14-Authentication Command message, the AN indicates to the AT that it wants to open the access stream by sending the Data Ready Indicator on the access stream. Note: The AT may turn off flow on the service stream (e.g., the flow control protocol for the default packet application bound to the PDSN is in the close state). The AT indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol for the default packet application bound to the AN is in the open state). e. The AT and the PCF initiate PPP and LCP negotiations for terminal authentication. The traffic is transmitted over the Ax connection established through step b and step c. Refer to [19]. This step is omitted when the PCF and AT keep the PPP connection after initial terminal authentication.

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

3-12

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

A.S0007-A v3.0 HRPD IOS

f.

The PCF generates a random challenge and sends it to the AT in a CHAP Challenge message in accordance with [23].

g. When the PCF receives the CHAP response message from the AT, it send an Access-Request message on the A12 Interface to the AN-AAA which acts as a RADIUS server in accordance with [25] (RADIUS). h. The AN-AAA looks up a password based on the User-name attribute in the Access-Request message and if the terminal authentication passes (as specified in [23] and [25]), the AN-AAA sends an Access-Accept message on the A12 interface in accordance with [25] (RADIUS). The Access-Accept message contains a RADIUS attribute with Type set to 20 (Callback-Id), which is set to the MN ID of the AT. Refer to section 2.3.2, AN-AAA Support. The PCF may ignore the MN ID received in the Access-Accept message in this case. i. j. The PCF returns an indication of CHAP terminal authentication success, to the AT. Refer to [23]. The PCF sends an A14-Authentication Completed message to the AN indicating that the authentication completed successfully and starts timer Tauthcomp14.

k. The AN sends an A14-Authentication Completed Ack message to the PCF. The PCF stops timer Tauthcomp14 upon receipt of the message. The AN and the PCF release the resources for the Ax connection. l. If necessary, the AT indicates that it is ready to exchange data on the service stream (e.g., the flow control protocol for the default packet application bound to the PDSN is in the open state).

3-13

A.S0007-A v3.0 HRPD IOS

May 2007

1

3.3

Data Delivery

2

This section describes the call flows associated with AT terminated and AT originated data delivery. 3.3.1 Successful Network Initiated Call Re-activation from Dormant State

3 4 5 6 7

In this scenario, it is assumed that the AT has already established a packet data session and also an HRPD session, however it does not have an HRPD connection and there is no A8 connection between the AN and the PCF. Two paging methods are specified and the Paging Type Indicator identifies which of the two paging methods is to be used. Refer to section 5.2.2.8, A14 Indicators, for a definition. 3.3.1.1 Paging Type 0 (Paging response is not required)

8 9 10

Figure 3.3.1.1-1 illustrates the call flow associated with network initiated call re-activation in the case of Paging Type Indicator set to `0'.

AT Source AN Target AN1 Target AN2 PCF PDSN time

Transmitting Packet Data A14-Paging Request A14-Paging Request Ack A15-Paging Request

x x

a b c

Tpreq14

d e

conditional

Page

Tpreq15

ConnectionRequest A15-Paging Response A15-Paging Response Ack A9-Setup-A8 A9-Connect-A8 Connection Establishment Transmitting Packet Data f g h i j k l conditional conditional

Tprsp15

TA8-setup

11 12

Figure 3.3.1.1-1

Successful Network Initiated Call Re-activation (Paging Type 0)

13 14 15 16 17 18 19 20

a. The PDSN sends packet data to the PCF. b. The PCF sends an A14-Paging Request message, including all session state information records, to the source AN to initiate paging and starts timer Tpreq14. The A14-Paging Request message includes the Paging Type Indicator set to `0' in this case. Note that the PCF may send the A14-Paging Request messages to multiple ANs. In this case, the PCF should set `A15 Paging Inhibited Indicator' to `1' to indicate not to perform inter-AN paging. If the `A15 Paging Inhibited Indicator' is set to `1', steps d, g and h are omitted and the connection request and establishment are via the source AN.

3-14

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

A.S0007-A v3.0 HRPD IOS

c. The source AN responds with an A14-Paging Request Ack message immediately after receiving the A14-Paging Request message. The PCF stops timer Tpreq14 upon receipt of the A14-Paging Request Ack message. d. If the source AN determines that inter-AN paging is required and the A15 Paging Inhibited Indicator bit is set to `0' in the A14-Paging Request message, the source AN sends an A15-Paging Request message to the target ANs. In this call flow, as an example, the source AN sends the A15-Paging Request message to AN1 and AN2. The source AN starts timer Tpreq15. e. The source AN, target AN1 and target AN2 each send a Page message to the AT, on the control channel. In this case, the Page message sent from target AN1 reaches the AT. f. The AT initiates connection establishment procedure by sending a ConnectionRequest message to target AN1. Note: Steps g and h may occur anytime after target AN1 detects the existence of the AT under its coverage. g. Target AN1 sends an A15-Paging Response message to the source AN and starts timer Tprsp15. Upon receipt of the message, the source AN stops timer Tpreq15. Note that step g and h are not performed if the source AN receives the ConnectionRequest message at step f. h. The source AN responds with an A15-Paging Response Ack message upon receipt of the A15-Paging Response message. Upon receipt of the A15-Paging Response Ack message, target AN1 stops timer Tprsp15. Note: Steps i and j may be performed without waiting for receipt of the A15-Paging Response Ack message. i. Target AN1 sends an A9-Setup-A8 message to the PCF with the Data Ready Indicator set to `1' to establish the A8 connection and starts timer TA8-setup. If target AN1 does not posses all the session information at this step, it includes the Session Information Required Indicator, set to `1', in the A9Setup-A8 message. The PCF sends an A9-Connect-A8 message to target AN1 and includes session information in the A9-Connect-A8 message if the Session Information Required Indicator was included and set to `1' in the A9-Setup-A8 message. When target AN1 receives the A9-Connect-A8 message it stops timer TA8-setup.

j.

k. Target AN1 assigns a Forward Traffic Channel. Reverse Power Control Channel and Reverse Traffic Channel. Refer to [10], for the Connection Setup State. This step may occur anytime after step f, once target AN possesses all the session information. l. At this point the connection is established and packet data can flow between the AT and the PDSN.

3-15

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3

3.3.1.2

Paging Type 1 (Paging response is required)

Figure 3.3.1.2-1 illustrates the call flow associated with network initiated call re-activation in the case of Paging Type Indicator set to `1'.

AT Source AN Target AN1 Target AN2 PCF PDSN time

Transmitting Packet Data A14-Paging Request A15-Paging Request

x x

a b c d conditional

Page

Tpreq15

Connection Request A15-Paging Response A15-Paging Response Ack A14-Paging Response

Tpage14 Tprsp15

e f g h i j k l conditional conditional

Tprsp14

A14-Paging Response Ack A9-Setup-A8 A9-Connect-A8 Connection Establishment Transmitting Packet Data

4 5

TA8-setup

m

Figure 3.3.1.2-1

Successful Network Initiated Call Re-activation (Paging Type 1)

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

a. The PDSN sends packet data to the PCF. b. The PCF sends an A14-Paging Request message, including session state information required to page, to the source AN to initiate paging and starts timer Tpage14. The A14-Paging Request message includes the Paging Type Indicator set to `1' in this case. Note that the PCF may send A14-Paging Request messages to multiple ANs. In this case, the PCF should set `A15 Paging Inhibited Indicator' to `1' to indicate not to perform inter-AN paging. If the `A15 Paging Inhibited Indicator' is set to `1', steps c, f and g are omitted and the connection request and establishment are via the source AN. c. If the source AN determines that inter-AN paging is required and `A15 Paging Inhibited Indicator' bit is set to `0' in the A14-Paging Request message, the source AN sends an A15-Paging Request message to the target ANs. In this call flow, as an example, the source AN determines that target AN1 and target AN2 are targets of the A15-Paging Request message. The source AN starts timer Tpreq15. d. The source AN, target AN1 and target AN2 each send a Page message to the AT, on the control channel. In this case, the Page message sent from target AN1 reaches the AT. e. The AT initiates connection establishment procedure by sending a ConnectionRequest message to target AN1. 3-16

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

A.S0007-A v3.0 HRPD IOS

Note: Step f and step g may occur anytime after target AN1 detects the existence of the AT under its coverage. f. Target AN1 sends an A15-Paging Response message to the source AN and starts timer Tprsp15. Upon receipt of the message, the source AN stops timer Tpreq15. Note that step f and g are not performed if the source AN receives the ConnectionRequest message at step e.

g. The source AN responds with an A15-Paging Response Ack message upon receipt of the A15-Paging Response message. Upon receipt of the A15-Paging Response Ack message, target AN1 stops timer Tprsp15. Note: Steps h and i may be performed without waiting for receipt of the A15-Paging Response Ack message. h. Target AN1 sends an A14-Paging Response message to the PCF, to indicate that it received the response from the AT, and starts timer Tprsp14. The PCF stops timer Tpage14 upon receipt of the message. i. The PCF sends an A14-Paging Response Ack message with all session state information records, to target AN1 in response to the A14-Paging Response message. Target AN1 stops timer Tprsp14 upon receipt of the message. Target AN1 sends an A9-Setup-A8 message to the PCF with the Data Ready Indicator set to `1' to establish the A8 connection and starts timer TA8-setup.

j.

k. The PCF sends an A9-Connect-A8 message to target AN1. When target AN1 receives the A9Connect-A8 message, it stops timer TA8-setup. l. Target AN1 assigns a Forward Traffic Channel. Reverse Power Control Channel and Reverse Traffic Channel. Refer to [10], for the Connection Setup State. This step may occur anytime after step i, once the target AN possesses all the session information.

m. At this point the connection is established and packet data can flow between the AT and the PDSN.

3-17

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3

3.3.2

AT Initiated Call Re-activation from Dormant State (Existing HRPD Session)

This scenario describes the data origination from a dormant AT. The AT has also established an HRPD session.

AT ConnectionRequest A9-Setup-A8 (Session information required) AN PCF PDSN time a b A11-Registration Request c d e f g

TA8-setup

Tregreq

A11-Registration Reply A9-Connect-A8 (Session State Information Record)

TrafficChannelAssignment TCH Establishment

Transmitting Packet Data

h

4 5

Figure 3.3.2-1 AT Initiated Call Re-activation from Dormant State (Existing HRPD Session) a. If the AT has data to send, the AT initiates connection establishment procedures with the AN. The AT sends a ConnectionRequest message to the AN to request establishment of a traffic channel. Refer to [10], section 6.4.5.6, Connection Setup State. b. The AN sends an A9-Setup-A8 message to the PCF with DRI set to `1' to establish the A8Connection and starts timer TA8-setup. Also, the Session Information Required field of the HRPD A9 Indicators information element in the A9-Setup-A8 message shall be set to `1' to get Session Information Record from the PCF. c. The PCF sends an A11-Registration Request message to send an Active Start accounting record and starts timer Tregreq. d. The PDSN sends an A11-Registration Reply message to the PCF. The PCF stops the timer Tregreq. e. The PCF sends the A9-Connect-A8 message with the Session State Information Record, to the AN. When the AN receives the A9-Connect-A8 message it stops timer TA8-setup. Refer to [11], section 2.14.7.6, MS Initiated Call Re-activation from Dormant State. f. The AN sends a TrafficChannelAssignment message to the AT to assign a traffic channel.

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

g. The AT and the AN establish the traffic channel. h. At this point the connection is established and packet data can flow between the AT and the PDSN.

3-18

May 2007

A.S0007-A v3.0 HRPD IOS

1

3.4

Connection Release

2

This section describes the call flows associated with an HRPD connection release. 3.4.1 Connection Release on HRPD Network - Initiated by the AT

3 4

This scenario describes the call flow associated with a connection release initiated by an AT.

AT Connection Release (initiated by the AT) AN PCF time a A9-Release-A8 (Session State Information Record (optional)) A9-Release-A8 Complete c b

Trel9

5 6

Figure 3.4.1-1 AT Initiated Connection Release a. The AT initiates HRPD connection release. Refer to [10], section 6, Connection Layer. b. The AN sends an A9-Release-A8 message with the cause value set to "Packet call going dormant", to the PCF to request the PCF to release the A8 connection. The AN includes a Session State Information Record in the A9-Release-A8 message if needed. The AN starts timer Trel9. c. The PCF initiates procedures for releasing the A8 connection and sends an A9-Release-A8 Complete message to the AN. The AN stops timer Trel9. At this time the A10 connection for this call is retained.

7 8 9 10 11 12 13

14 15

3.4.2

Connection Release on HRPD Network - Initiated by the AN

This scenario describes the call flow associated with a connection release initiated by the AN.

AT AN A9-Release-A8 (Session State Information Record (optional)) A9-Release-A8 Complete Connection Release (initiated by the AN) b c PCF time a

Trel9

16 17

Figure 3.4.2-1 AN Initiated Connection Release a. The AN initiates release of the A8 connection by transmitting an A9-Release-A8 message to the PCF with the cause value set to "Packet call going dormant". The AN includes a Session State Information Record in the A9-Release-A8 message. The AN starts timer Trel9. b. The PCF responds to the A9-Release-A8 message with an A9-Release-A8 Complete message. The AN stops timer Trel9. c. The AN initiates HRPD connection release. This step may occur in parallel with steps a and b. Refer to [10], section 6, Connection Layer.

18 19 20 21 22 23 24

3-19

A.S0007-A v3.0 HRPD IOS

May 2007

1 2

3.4.3

Connection Release on HRPD Network - Initiated by the PCF

This scenario describes the call flow associated with a connection release initiated by the PCF.

AT AN A9-Disconnect-A8 Connection Release (initiated by the AN) PCF time a

Tdiscon9

A9-Release-A8 (Session State Information Record (optional)) A9-Release-A8 Complete

b c d

Trel9

3 4

Figure 3.4.3-1 PCF Initiated Connection Release a. The PCF sends an A9-Disconnect-A8 message to the AN, with a cause value set to "Packet call going dormant", to request the release of the A8 connection and starts timer Tdiscon9. b. The AN initiates HRPD connection release. Refer to [10], section 6, Connection Layer. c. The AN initiates release of the A8 connection by transmitting an A9-Release-A8 message to the PCF with the cause value set to "Packet call going dormant", to request the PCF to release the associated dedicated resources. The AN includes a Session State Information Record in the A9-Release-A8 message, if needed. The PCF stops timer Tdiscon9 upon receipt of the A9-Release-A8 message. The AN starts timer Trel9. d. The PCF responds to the A9-Release-A8 message with an A9-Release-A8 Complete message. The AN stops timer Trel9.

5 6 7 8 9 10 11 12 13 14 15

16 17

3.4.4

Connection Release Caused by Air Link Lost

This scenario describes the call flow associated with connection release caused by air link lost.

AT AN PCF PDSN time

Active HRPD Session AN loses air link to the AT A9-Release-A8 (Cause: Air Link Lost) A11-Registration Request A11-Registration Reply A9-Release-A8 Complete a b c d e

Trel9

18 19

Figure 3.4.4-1

Connection Release Caused by Air Link Lost

20 21 22

a. The AN determines that it is not receiving any transmissions from the AT. b. The AN sends an A9-Release-A8 message with the cause value indicating `Air link lost', to the PCF and starts timer Trel9. 3-20

May 2007

1 2 3 4 5 6 7 8 9

A.S0007-A v3.0 HRPD IOS

c. The PCF sends an A11-Registration Request message to the PDSN with a Lifetime timer value of zero to close the A10 connection. Accounting data is included in the message. The PCF starts timer Tregreq. d. The PDSN stores the accounting data and responds with an A11-Registration Reply message to complete the release of the A10 connection. The PCF stops timer Tregreq. e. The PCF responds to the A9-Release-A8 message with an A9-Release-A8 Complete message. The AN stops timer Trel9. The PCF should not attempt to re-page the AT immediately upon receipt of the A9-Release-A8 message with cause value `Air link lost'.

3-21

A.S0007-A v3.0 HRPD IOS

May 2007

1

3.5

HRPD Session Release

2

This section describes the call flows associated with HRPD session release. 3.5.1 HRPD Session Release - Initiated by the AT (A8 Connection Exists)

3 4 5 6

This scenario describes the call flows associated with an HRPD session release initiated by an AT. This subsequently leads to a packet data session release, if present. It is assumed that the A8 connection is already established.

AT AN PCF PDSN time

Session Release (initiated by the AT) A9-Release-A8 (Session State Information Record)

a b A11-Registration Request (Lifetime=0, Acct data) A11-Registration Reply (Lifetime=0, Accept) A9-Release-A8 Complete c d e

Trel9

Tregreq

7 8

Figure 3.5.1-1 AT Initiated HRPD Session Release (A8 Connection Exists) a. The AT initiates HRPD session release. Refer to [10], section 5, Session Layer. b. After the AN closes the HRPD session, the AN sends an A9-Release-A8 message with a Session State Information Record (optional) and a cause value set to "Normal call release" to the PCF to request the PCF to release the associated dedicated resource and the associated A10 connection. The AN starts timer Trel9. c. The PCF sends an A11-Registration Request message to the PDSN with a Lifetime timer value of zero to close the A10 connection. Accounting data is included in the message. The PCF starts timer Tregreq. Refer to [11], section 2.15.5.6, Packet Data Service Session Clearing - MS Initiated. d. The PDSN stores the accounting data for further processing and responds with an A11-Registration Reply message to complete the release of the A10 connection. The PCF stops timer Tregreq. e. The PCF sends an A9-Release-A8 Complete message to the AN. The AN stops timer Trel9.

9 10 11 12 13 14 15 16 17 18 19 20

3-22

May 2007

A.S0007-A v3.0 HRPD IOS

1 2 3 4

3.5.2

HRPD Session Release - Initiated by the AT (A8 Connection does not Exist)

This scenario describes the call flows associated with an HRPD session release initiated by an AT. This subsequently leads to a packet data session release, if present. It is assumed that there is no A8 connection for this AT.

AT AN PCF PDSN time

Session Release (initiated by the AT) A14-Session Release

a b

Trel14

Tregreq

A11-Registration Request (Lifetime=0) A11-Registration Reply (Lifetime=0, Accept)

c d e

conditional conditional

A14-Session Release Complete

5 6

Figure 3.5.2-1 AT Initiated HRPD Session Release (A8 Connection does not Exist) a. The AT initiates HRPD session tear-down. Refer to [10], section 5, Session Layer. b. After the AN closes the HRPD session, the AN sends an A14-Session Release message to the PCF to request the PCF to release the associated dedicated resource and the associated A10 connection. The AN starts timer Trel14. Note: Steps c and d are performed if the A10 connection exists. c. The PCF sends an A11-Registration Request message to the PDSN with a Lifetime timer value of zero to close the A10 connection. The PCF starts timer Tregreq. Refer to [11], section 2.15.5.6, Packet Data Service Session Clearing - MS Initiated. d. The PDSN responds with an A11-Registration Reply to complete the release of the A10 connection. The PCF stops timer Tregreq. e. The PCF sends an A14-Session Release Complete message to the AN. The AN stops timer Trel14.

7 8 9 10 11 12 13 14 15 16 17 18

3-23

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3 4

3.5.3

HRPD Session Release - Initiated by the AN (A8 Connection Exists)

This scenario describes the call flow associated with an HRPD session release initiated by the AN. This subsequently leads to a packet data session release, if present. It is assumed that an A8 connection exists for the AT.

AT Session Release (initiated by the AN) A9-Release-A8 (Session State Information Record) AN PCF PDSN time

a b A11-Registration Request (Lifetime=0, Acct data) A11-Registration Reply (Lifetime=0, Accept) A9-Release-A8 Complete c d e

Trel9

Tregreq

5 6

Figure 3.5.3-1 AN Initiated HRPD Session Release (A8 Connection Exists) a. The AN initiates HRPD session release. Refer to [10], section 5, Session Layer. b. The AN sends an A9-Release-A8 message with a session information record (optional) and a cause value set to "Normal call release" to the PCF to request the PCF to release the associated dedicated resource and the associated A10 connection. The AN starts timer Trel9. c. The PCF sends an A11-Registration Request message, with Lifetime set to zero, to the PDSN. Accounting data is included in the message. The PCF starts timer Tregreq. d. The PDSN sends an A11-Registration Reply message to the PCF. The PCF closes the A10 connection for the AT and stops timer Tregreq. e. The PCF sends an A9-Release-A8 Complete message to the AN. The AN stops timer Trel9.

7 8 9 10 11 12 13 14 15 16

3-24

May 2007

A.S0007-A v3.0 HRPD IOS

1 2 3

3.5.4

HRPD Session Release - Initiated by the PCF (A8 Connection Exists)

This scenario describes the call flow associated with an HRPD Session Release initiated by the PCF. It is assumed that an A8 connection exists for the AT.

AT AN A9-Disconnect-A8 Session Release A9-Release-A8 PCF PDSN time a b c

Tdiscon9

Trel9

Tregreq

A11-Registration Request (Lifetime=0, Acct data) A11-Registration Reply (Lifetime=0, Accept)

d e f

A9-Release-A8 Complete

4 5

Figure 3.5.4-1 PCF Initiated HRPD Session Release (A8 Connection Exists) a. The PCF sends an A9-Disconnect-A8 message to the AN, with a cause value set to "Normal call release", and starts timer Tdiscon9. b. The AN initiates HRPD session tear-down. Refer to [10], section 5, Session Layer. c. The AN sends an A9-Release-A8 message with the cause value set to "Normal call release", to the PCF to request the PCF to release the associated dedicated resources. The AN starts timer Trel9. The PCF stops timer Tdiscon9. d. The PCF sends an A11-Registration Request message, with Lifetime set to zero, to the PDSN. Accounting data is included in the message. The PCF starts timer Tregreq. e. The PDSN sends an A11-Registration Reply message to the PCF. The PCF closes the A10 connection for the AT and stops timer Tregreq. f. The PCF responds to the A9-Release-A8 message with an A9-Release-A8 Complete message. The AN stops timer Trel9.

6 7 8 9 10 11 12 13 14 15 16 17 18

3-25

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3 4

3.5.5

HRPD Session Release - Initiated by the PCF (A8 Connection does not Exist)

This scenario describes the call flow associated with an HRPD Session Release initiated by the PCF. This procedure is used when the A8 connection does not exist and the PCF decides that the HRPD session should be released.

AT AN A14-Session Release Command Session Release A14-Session Release PCF PDSN time a b c A11-Registration Request (Lifetime=0) A11-Registration Reply (Lifetime=0, Accept) A14-Session Release Complete d conditional e conditional f

Trelcom14

Trel14

Tregreq

5 6

Figure 3.5.5-1 PCF Initiated HRPD Session Release (A8 Connection does not Exist) a. The PCF sends an A14-Session Release Command message to the AN and starts timer Trelcom14. b. The AN initiates HRPD session tear-down. Refer to [10], section 5, Session Layer. c. The AN sends an A14-Session Release message to the PCF to request the PCF to release the associated dedicated resources. The AN starts timer Trel14. The PCF stops timer Trelcom14. Note: Steps d and e are performed if the A10 connection exists. d. The PCF sends an A11-Registration Request message, with Lifetime set to zero, to the PDSN. The PCF starts timer Tregreq. e. The PDSN sends an A11-Registration Reply message to the PCF. The PCF closes the A10 connection for the AT and stops timer Tregreq. f. The PCF responds to the A14-Session Release message with an A14-Session Release Complete message. The AN stops timer Trel14.

7 8 9 10 11 12 13 14 15 16 17 18

3-26

May 2007

A.S0007-A v3.0 HRPD IOS

1

3.6

Packet Data Session Release - Initiated by the PDSN

2 3

This scenario describes the call flow associated with an A10 release initiated by the PDSN. This procedure shall be executed when the PDSN closes the packet data (PPP) session.

AT AN PCF A11-Registration Update PDSN time a

Tregupd

A11-Registration Acknowledge A11-Registration Request (Lifetime=0) b c

Tregreq

A11-Registration Reply (Lifetime=0, accept) d

Session Release or Connection Release

e

Optional

4 5

Figure 3.6-1

PDSN Initiated Packet Data Session Release

6 7 8 9 10 11 12 13 14 15 16 17 18

a. The PDSN initiates closure of the A10 connection by sending an A11-Registration Update message to the PCF. The PDSN starts timer Tregupd. b. The PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer Tregupd. c. The PCF sends an A11-Registration Request message, with Lifetime set to zero, to the PDSN. The PCF starts timer Tregreq. d. The PDSN sends an A11-Registration Reply message to the PCF. The PCF closes the A10 connection for the AT and stops timer Tregreq. e. If the PCF decides that the HRPD session should also be released, the PCF initiates the HRPD session release procedure (refer to section 3.5.4 (A8 Connection Exists) or section 3.5.5 (A8 Connection does not Exist)). If the PCF decides that only the connection should be released, the PCF initiates the connection release procedure (refer to section 3.4.3). This step may not occur when the A8 connection does not exists and the PCF decides that HRPD session should be kept.

3-27

A.S0007-A v3.0 HRPD IOS

May 2007

1

3.7

Dormant Handoff of HRPD AT between PCFs - Served by the Same PDSN

2 3

This section describes the call flows associated with AT dormant handoff between PCFs that are served by the same PDSN. 3.7.1 PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information

4 5 6 7

This scenario describes the call flow associated with a dormant handoff between PCFs when the HRPD session information is successfully retrieved over the A13 interface. It is assumed that the AT has crossed a mobility boundary.

AT Target AN Target PCF Source PCF PDSN time

Initiate Session Establishment A14-UATI Request A13-Session Info Request

a b c d e

T14-UATI-Req

TA13req

A13-Session Info Response

A14-UATI Assignment Complete Session Establishment

T14-UATI-Assign

A14-UATI Complete

TA13res

f g

T14-UATI-Comp

A14-UATI Complete Ack

A13-Session Info Confirm

h i

Tregreq

A11-Registration Request (Lifetime, MEI) A11-Registration Reply (Lifetime, accept) A11-Registration Update A11-Registration Ack. A11-Registration Request (Lifetime=0) A11-Registration Reply (Lifetime=0, accept)

j k l

Tregupd

m n

Tregreq

o

8 9

Figure 3.7.1-1

Inter-PCF/Intra-PDSN Dormant PCF-PCF HO - Successful Operation

10 11 12 13 14 15 16 17 18

a. The AT and the target AN initiate HRPD session establishment. b. The target AN sends an A14-UATI Request message to the target PCF. The PCF determines that HRPD session information is required for the AT. The target AN starts timer T14-UATI-Req. c. The target PCF determines the UATI of an existing HRPD session (if available). The UATI may be used as an identifier for the existing HRPD session when the target PCF attempts to retrieve the existing HRPD session State Information from the Source PCF. The target PCF sends an A13-Session Information Request message to the source PCF to request the HRPD session information for the AT. The A13-Session Information Request message shall include the determined UATI, the Security Layer Packet and Sector ID. The target PCF starts timer TA13req. 3-28

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

A.S0007-A v3.0 HRPD IOS

d. The source PCF validates the A13-Session Information Request and sends the requested HRPD session information of the AT to the target PCF in an A13-Session Information Response message. The source PCF starts timer TA13res.The target PCF stops timer TA13req. e. The target PCF sends an A14-UATI Assignment message to the target AN and starts timer T14-UATIAssign. The target AN stops timer T14-UATI-Req. f. The AT and the target AN complete the establishment of the HRPD session. Depending on the state of the AT and the target AN, either an existing HRPD session may be re-established, or a new HRPD session may be initiated if required. This step may be null if no further over-the-air signaling is required.

g. On completion of the session establishment procedures, the target AN sends an A14-UATI Complete message to the target PCF indicating that the UATI assignment was successful. The target PCF stops timer T14-UATI-Assign and the target AN starts timer T14-UATI-Comp. h. The target PCF sends an A13-Session Information Confirm to the source PCF to indicate that the target PCF has received the HRPD session information. Upon receipt of the A13-Session Information Confirm message the source PCF deletes the associated AT HRPD session information. The source PCF stops timer TA13res. i. j. The target PCF sends an A14-UATI Complete Ack message to the target AN as response to the A14UATI Complete message. The target AN stops timer T14-UATI-Comp. The target PCF selects the PDSN using the PDSN address provided in the A13-Session Information Response message or using PDSN selection algorithms as specified in [11], and sends an A11Registration Request message to the PDSN. The A11-Registration Request message includes the MEI within the CVSE and PANID/CANID within the NVSE. The target PCF starts timer Tregreq. Refer to [11], section 2.15.5.8, Inter-PCF Dormant Handoff - Mobile Continues to be Served by the Serving PDSN.

k. The A11-Registration Request message is validated and the PDSN accepts the connection by returning an A11-Registration Reply message with an accept indication and the Lifetime set to the configured Trp value. If the PDSN has data to send, it includes the Data Available Indicator within the CVSE. The A10 connection binding information at the PDSN is updated to point to the target PCF. The target PCF stops timer Tregreq. l. The PDSN initiates closure of the A10 connection with the source PCF by sending an A11-Registration Update message. The PDSN starts timer Tregupd.

m. The source PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer Tregupd. n. The source PCF sends an A11-Registration Request message, with Lifetime set to zero, to the PDSN. The source PCF starts timer Tregreq. o. The PDSN sends an A11-Registration Reply message to the source PCF. The source PCF closes the A10 connection for the AT and stops timer Tregreq.

3-29

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3

3.7.2

Dormant PCF-PCF Handoff with HRPD Session Information Transfer Failure

This scenario describes the call flow associated with a dormant handoff between PCFs when the HRPD session information can not be retrieved successfully from the source PCF.

AT Target AN Initiate Session Establishment A14-UATI Request A13-Session Information Request Target PCF Source PCF PDSN time

a b c d e f Initial AT Origination g

T14UATI-Req

TA13req

A13-Session Information Reject

A14-UATI Assignment Failure SessionClose

4 5

Figure 3.7.2-1

Inter-PCF/Intra-PDSN Dormant PCF-PCF HO - Transfer Failure

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

a. The AT and the target AN initiate HRPD session establishment. b. The target AN sends an A14-UATI Request message to inform the target PCF that a new HRPD session is required for the AT. The target AN starts timer T14-UATI-Req. c. The target PCF determines the UATI of an existing HRPD session (if available). The UATI can be used as an identifier for the existing HRPD session when the target PCF attempts to retrieve the existing HRPD session state information from the source PCF. The target PCF sends an A13-Session Information Request message to the source PCF to request the HRPD session information for the AT. The A13-Session Information Request message includes the determined UATI and the received Security Layer Packet. The target PCF starts timer TA13req. d. The source PCF cannot validate the A13-Session Information Request or does not have the requested AT HRPD session information and sends an A13-Session Information Reject message to the target PCF. The target PCF stops the timer TA13req. e. The target PCF sends an A14-UATI Assignment Failure message to inform the target AN that the source PCF can not validate the A13-Session Information Request message. The target AN stops timer T14-UATI-Req. f. The target AN sends a SessionClose message to the AT to close the HRPD session.

g. The AT initiates Initial AT Origination procedure. Refer to section 3.1.1. Note that during this procedure the PDSN releases the A10 connection to the source PCF.

3-30

May 2007

A.S0007-A v3.0 HRPD IOS

1

3.8

Active HRPD Session

2

This section describes the call flows associated with an active HRPD session. 3.8.1 Deactivation/Activation of Data Flow During an Active HRPD Session

3 4 5

This scenario describes the call flow associated with the deactivation and activation of A8 traffic data flow during an active HRPD session.

AT AN PCF PDSN time

Active HRPD Session

Data A9-AL Disconnected

Data

a b c

Tald9

A9-AL Disconnected Ack

Data A9-AL Connected

d e f

Talc9

A9-AL Connected Ack Data

6 7

Data

g

Figure 3.8.1-1

Activation /De-activation of Data Flow During Active HRPD Session

8 9 10 11 12 13 14 15 16 17 18 19

a. The PDSN transfers data to the AN through the PCF during an active HRPD session. b. The AN determines that it is preferable not to receive A8 traffic data from the PCF, and the AN sends an A9-AL Disconnected message to the PCF to stop the data flow and starts timer Tald9. c. Upon receipt of the A9-AL Disconnected message the PCF sends an A9-AL Disconnected Ack message to the AN. The AN stops timer Tald9. d. The PCF stops the data flow and may buffer data received from the PDSN. e. When the AN determines that it is preferable for the data flow to resume, the AN sends an A9-AL Connected message to PCF and starts timer Talc9. f. The PCF responds to the AN with an A9-AL Connected Ack message. The AN stops timer Talc9.

g. The PCF resumes transmitting data received from the PDSN and buffered data if it exists.

3-31

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3

3.8.2

Session Information Update During an Active HRPD Session

This scenario describes the call flow associated with updating session information during an active HRPD session.

AN PCF time

A14-Session Information Update

a b

Tsu14

A14-Session Information Update Ack

4 5 6 7 8 9 10 11

Figure 3.8.2-1 Session Information Update During an Active HRPD Session a. When the AN determines that updated session information should be transferred to the PCF, the AN sends an A14-Session Information Update message to the PCF. The AN starts timer Tsu14. b. The PCF sends an A14-Session Information Update Ack message to the AN in response to the A14Session Information Update message. The AN stops timer Tsu14 upon receipt of the A14-Session Information Update Ack message.

3-32

May 2007

A.S0007-A v3.0 HRPD IOS

1

3.9

Mobility Management

2

This section describes the call flows associated with mobility management. 3.9.1 Route Updating of a dormant AT

3 4 5 6 7 8 9 10

This scenario describes the call flow associated with a route updating procedure. This scenario occurs when: · the dormant AT moves a certain distance 2 from the AN where it last performed the route updating procedure, or · the dormant AT sends a message on the access channel (e.g., XonRequest, KeepAliveRequest). This procedure does not apply when the AN receives a ConnectionRequest message with the RouteUpdate message.

AT RouteUpdate (Response message) A14-General Update AN PCF time a b c d Optional

Tgu14

A14-General Update Complete

11 12

Figure 3.9.1-1 Route Updating of a Dormant AT a. The AT sends a RouteUpdate message to the AN. One or more other messages (e.g., XonRequest, XoffRequest, KeepAliveRequest, KeepAliveResponse, LocationNotification) may be bundled with this RouteUpdate message. b. If the AN receives the message requiring a response message, the AN sends a response message to the AT. E.g., the AN sends a KeepAliveResponse message when it receives a KeepAliveRequest message from the AT. c. The AN sends an A14-General Update message including Sector ID to the PCF upon receipt of the RouteUpdate message and starts timer Tgu14. If the AN receives a KeepAliveRequest message with the RouteUpdate message, the AN includes the Keep Alive Indicator set to `1' in the A14-General Update message. If the AN receives any other message with the RouteUpdate message, that changes state information for a configured protocol, the AN includes the Session State Information Record in the A14-General Update message to notify that a state change has occurred. d. The PCF registers the AT's current location and sends an A14-General Update Complete message to respond to the A14-General Update message. The AN stops timer Tgu14.

13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

2

This distance is determined in [10].

3-33

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3 4

3.9.2

Session Keep Alive Procedure of a dormant AT ­ Initiated by the PCF

This scenario describes the call flow associated with the session keep alive procedure initiated by the PCF when the AT is in the dormant state. The session keep alive procedure initiated by the AT shall apply the procedure described in section 3.9.1.

AT AN A14-Keep Alive Request PCF time a

Tkareq14

A14-Keep Alive Request Ack KeepAliveRequest Route Update Procedure

5 6

b c d

Figure 3.9.2-1 Session Keep Alive Procedure of a Dormant AT ­ Initiated by the PCF a. When the PCF decides to check the availability of the current session, it sends an A14-Keep Alive Request message to the AN to maintain the current session and starts timer Tkareq14. b. The AN sends an A14-Keep Alive Request Ack message to acknowledge the A14-Keep Alive Request message. The PCF stops timer Tkareq14. c. The AN sends a KeepAliveRequest message to the AT. d. The route updating procedure described in section 3.9.1 is performed to process the reply message from the AT.

7 8 9 10 11 12 13 14 15 16

3-34

May 2007

1

A.S0007-A v3.0 HRPD IOS

4 HRPD and 1x IOS Transition Call Flows

This section describes the call flows associated with handoffs between HRPD and 1x systems for hybrid MS/ATs. Where the BS and PCF are combined into one entity in this section, it is assumed that the messaging on A8/A9 is identical to the corresponding call flows in section 3. While specific air interface messages may be identified in the HRPD IOS call flows, they are provided only for AN trigger references. Refer to [10] for the definitions and formats of these messages. For simplicity, the 1x and HRPD transition scenarios (sections 4.1 and 4.2) do not show interactions with the MSC.

2 3 4 5 6 7 8

9 10 11

4.1

Dormant Cross System Handoff - MS/AT Served by the Same PDSN.

This section describes the call flows for dormant handoffs between HRPD and 1x systems. In this section it is assumed that the source PCF and target PCF are distinct entities. 4.1.1 1x to HRPD Dormant Packet Data Session Handoff - Existing HRPD Session

12 13 14 15 16 17 18 19 20 21

This scenario describes the call flow associated with an MS/AT dormant handoff from a 1x to an HRPD system, when the HRPD system supports unsolicited Location Notification messages. Refer to [10]. Based on a detected change of ANID or for other reasons, a dormant handoff from 1x to HRPD is determined to be required. In this scenario, it is assumed that the MS/AT has already established an HRPD session however it does not have a connection established. In addition, the MS/AT is configured to send unsolicited location notifications upon return to the HRPD system. This call flow assumes that no HRPD mobility boundary has been crossed since the MS/AT last reported a mobility event to any HRPD system. If an HRPD mobility boundary has been crossed, the call flow is as described in section 3.7.1, PCF-PCF Dormant Handoff with Successful Retrieval of HRPD Session Information.

MS/AT Target AN Source BS/PCF Target PCF PDSN time

LocationNotification A14-General Update A11-Registration Request (Lifetime, MEI) A11-Registration Reply (Lifetime, accept)

a b c d

Tgu14

Tregreq

A14-General Update Complete LocationAssignment LocationComplete A11-Registration Update A11-Registration Acknowledge A11-Registration Request (Lifetime=0)

e f g h

Tregupd

i j k

Tregreq

A11-Registration Reply (Lifetime=0, accept)

22 23

Figure 4.1.1-1 1x to HRPD Dormant Packet Data Session HO - Existing HRPD Session

4-1

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

May 2007

a. The MS/AT sends a LocationNotification message to the target AN when it moves from a 1x to an HRPD system. b. The target AN sends an A14-General Update message, with the Access Network Identifier set to the PANID stored in the AT, to the target PCF and starts timer Tgul4. c. If the PDSN address is not available to the target PCF by other means, the target PCF selects a PDSN for this connection using the PDSN selection algorithm as specified in [10]. The target PCF sends an A11-Registration Request message to the PDSN. The A11-Registration Request message includes the MEI within the CVSE and the PANID of the source PCF and the Current Access Network Identifiers (CANID) of the target PCF, within the NVSE. The target PCF starts timer Tregreq. d. The A11-Registration Request message is validated and the PDSN accepts the connection by returning an A11-Registration Reply message with an accept indication and the Lifetime set to the configured Trp value. If the PDSN has data to send, it includes the Data Available Indicator within the CVSE. The A10 connection binding information at the PDSN is updated to point to the target PCF. The target PCF stops timer Tregreq. e. The target PCF responds to the target AN with an A14-General Update Complete message. The target AN stops timer Tgul4. f. The target AN sends a LocationAssignment message to the AT.

g. The AT responds with a LocationComplete message to the target AN. h. The PDSN initiates closure of the A10 connection with the source BS/PCF by sending an A11-Registration Update message. The PDSN starts timer Tregupd. i. j. The source BS/PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer Tregupd. The source BS/PCF sends an A11-Registration Request message, with Lifetime set to zero, to the PDSN. The source BS/PCF starts timer Tregreq.

k. The PDSN sends an A11-Registration Reply message to the source BS/PCF. The source BS/PCF closes the A10 connection for the MS/AT and stops timer Tregreq.

4-2

May 2007

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5

4.1.2

1x to HRPD Dormant Packet Data Session Handoff - New HRPD Session

This scenario describes the call flow associated with an MS/AT dormant handoff from a 1x to an HRPD system. Based on an MS/AT report that it crossed a network specified threshold for signal strength or for other reasons, a dormant handoff from 1x to HRPD is determined to be required when the dormant MS/AT transitions from 1x to HRPD.

MS/ AT UATIRequest Target AN Source BS/PCF Target PCF AN AAA PDSN time a

T14-UATI-Req

UATIAssignment UATIComplete

A14-UATI Request A14-UATI Assignment

b c d e

T14-UATI-Assign T14-UATI-Comp

A14-UATI Complete A14-UATI Complete Ack

f g h

ConnectionRequest

TA8-setup

A9-Setup-A8 (DRI=1) A9-Release-A8 Complete (Authentication required, Session Information (Default))

i j k

TCH Establishment

Session Negotiation Connection Release

l

m

Tsu14

ConnectionRequest TCH Establishment

A14-Session Info Update A14-Session Info Update Ack

n o p q

Tauthreq14

AT or AN indicates ready to exchange data on access stream

A14-Authentication Request A14-Authentication Response

r s t

PPP and LCP Negotiation

u

CHAP Challenge - Response

v

6 7

Figure 4.1.2-1 1x to HRPD Dormant Packet Data Session Handoff - New HRPD Session

4-3

A.S0007-A v3.0 HRPD IOS

MS/ AT Target AN Source BS/PCF Target PCF AN AAA

May 2007

PDSN time

A12 Access-Request A12 Access-Accept CHAP - Authentication Success A14-Authentication Completed (Authentication Succeded) A14-Authentication Completed Ack Location update procedure AT ready to exchange data on service stream A9-Setup-A8 (DRI=1)

w x y z

Tauthcomp14

aa bb

cc dd A11-Registration Request A11-Registration Reply ee ff gg A11-Registration Update A11-Registration Acknowledge A11-Registration Request (Lifetime=0) A11-Registration Reply (Lifetime=0, accept) hh

TA8-setup

A9-Connect-A8

Tregreq

Tregupd

ii jj

Tregreq

kk

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

Figure 4.1.2-1 1x to HRPD Dormant Packet Data Session Handoff - New HRPD Session Continued a. The MS/AT sends a UATIRequest message with a RATI to request that a UATI be assigned to it. b. The target AN sends an A14-UATI Request message to the target PCF to request the target PCF to assign a UATI for the MS/AT. The target AN starts timer T14-UATI-Req. c. Upon receipt of the A14-UATI Request message, the target PCF assigns a UATI for the MS/AT from its UATI pool, sends an A14-UATI Assignment message including the assigned UATI and starts timer T14-UATI-Assign. The target AN stops timer the T14-UATI-Req upon receipt of this message. d. The target AN sends a UATIAssignment message to assign the UATI to the MS/AT. e. The MS/AT sends a UATIComplete message to notify the target AN that it has received the UATIAssignment message. f. Upon receipt of the UATIComplete message from the MS/AT, the target AN sends an A14-UATI Complete message to the target PCF to notify the target PCF that UATI assignment completed successfully. The target AN starts timer T14-UATI-Comp. The target PCF stops timer T14-UATI-Assign upon receipt of the A14-UATI Complete message.

g. The target PCF sends an A14-UATI Complete Ack message to the target AN as an acknowledgment. The target AN stops timer T14-UATI-Comp. h. The MS/AT sends a ConnectionRequest message to the target AN to request TCH establishment. i. j. The target AN sends an A9-Setup-A8 message to the target PCF with Data Ready Indicator (DRI) set to `1', to establish the A8 connection. The target AN starts timer TA8-setup. Upon receipt of the A9-Setup-A8 message, the target PCF checks the status of the MS/AT, determines that terminal authentication is required and sends an A9-Release-A8 Complete message to 4-4

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45

A.S0007-A v3.0 HRPD IOS

the AN. This message contains session information. In this case default configurations are used for the session information. The target AN stops timer TA8-setup. k. The MS/AT and the target AN establish a TCH. l. The MS/AT and the target AN initiate the HRPD session negotiation procedure. If a key exchange procedure is requested during the session negotiation, the MS/AT and the target AN initiate a key exchange procedure.

m. After the session negotiation between the MS/AT and the target AN, the initial connection is released. n. The target AN sends an A14-Session Information Update message to the PCF to update the negotiated session information at the PCF. The target AN starts timer Tsu14. o. The PCF responds with an A14-Session Information Update Ack message to acknowledge the A14Session Information Update message from the target AN. The target AN stops timer Tsu14 upon receipt of this message. p. The MS/AT sends a ConnectionRequest message to the target AN. q. The MS/AT and the target AN establish a TCH. r. The target AN sends an A14-Authentication Request message to the target PCF to indicate the resource (i.e. IP address and GRE key) for the authentication at the target AN. The target AN starts timer Tauthreq14. The target PCF sends an A14-Authentication Response message to the target AN to indicate the resource (i.e. IP address and GRE key) for the authentication at the target PCF. The target AN stops timer Tauthreq14 upon receipt of the A14-Authentication Response message. The MS/AT or the target AN indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol for the default packet application bound to the target AN is in the open state). Note that this step may occur any time after step `q'.

s.

t.

u. The MS/AT initiates PPP and LCP negotiations for terminal authentication. Refer to [19]. v. The target PCF generates a random challenge and sends it to the MS/AT in a CHAP Challenge message in accordance with [23]. w. When the target PCF receives the CHAP response message from the MS/AT, it sends an AccessRequest message on the A12 interface to the AN-AAA which acts as a RADIUS server in accordance with [25]. x. The target AN-AAA looks up a password based on the User-name attribute in the Access-Request message and if the terminal authentication passes (as specified in [23] and [25]), the AN-AAA sends an Access-Accept message on the A12 interface in accordance with [25] (RADIUS). The AccessAccept message contains a RADIUS attribute with Type set to 20 (Callback-Id), which is set to the MN ID of the AT. Refer to section 2.3.2, AN-AAA Support. y. The target PCF returns an indication of CHAP terminal authentication success to the MS/AT. Refer to [23]. z. The target PCF sends an A14-Authentication Completed message indicating that the authentication completed successfully and starts timer Tauthcomp14. aa. The target AN sends an A14-Authentication Completed Ack message to the target PCF. The target PCF stops timer Tauthcomp14 upon receipt of the message. bb. The target AN retrieves the PANID and updates the ANID in the MS/AT using the location update procedure. The target AN may send the LocationRequest message to the MS/AT and the MS/AT may send the LocationNotification message in an unsolicited manner during this procedure when the configuration attribute value of the Handoff Indicator for the default packet application type bound to the RAN is set to `1'. 4-5

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

May 2007

cc. The MS/AT indicates that it is ready to exchange data on the service stream. (E.g., the flow control protocol for the default packet application bound to the packet data network is in the open state). dd. The target AN sends an A9-Setup-A8 message to the target PCF with Data Ready Indicator (DRI) set to `1' to establish the A8-Connection and starts timer TA8-setup. ee. The target PCF sends an A11-Registration Request message to the PDSN. The A11-Registration Request message includes the MEI within the CVSE and the PANID of the source and the CANID of the target PCF within the NVSE. If PANID is not sent in step bb, the target PCF sets all of the fields within the PANID and the CANID to zero. The target PCF starts timer Tregreq. ff. The A11-Registration Request message is validated and the PDSN accepts the connection by returning an A11-Registration Reply message with an accept indication and Lifetime set to the configured Trp value. If the PDSN has data to send it includes the Data Available Indicator within the CVSE. The A10 connection binding information at the PDSN is updated to point to the target PCF. The target PCF stops timer Tregreq. gg. Upon establishment of the A10 connection, the target PCF establishes an A8 connection and transmits an A9-Connect-A8 message with cause value set to `Successful Operation'. The target AN stops timer TA8-setup upon receipt of this message. hh. The PDSN initiates closure of the A10 connection with the source BS/PCF by sending an A11-Registration Update message. The PDSN starts timer Tregupd. ii. The source BS/PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer Tregupd. jj. The source BS/PCF sends an A11-Registration Request message, with Lifetime set to zero, to the PDSN. The source BS/PCF starts timer Tregreq. kk. The PDSN sends an A11-Registration Reply message to the source BS/PCF. The source BS/PCF closes the A10 connection for the MS/AT and stops timer Tregreq.

4-6

May 2007

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7

4.1.3

HRPD to 1x Dormant Packet Data Session Handoff

This scenario describes the call flow associated with an MS/AT dormant handoff from an HRPD to a 1x system. Based on a detected change of ANID or for other reasons, a dormant handoff from HRPD to 1x is determined to be required. In this scenario, it is assumed that the MS/AT has already established an HRPD session, and hence a packet data session, however it does not have a connection established. Moreover, it is assumed that the default HRPD SR_ID (=1) matches the SR_ID used in the 1x system, and that the MN_ID used in the HRPD system is the MS IMSI.

MS/AT Origination (DRS='0') Target BS/PCF Source AN/PCF PDSN time a

BS Ack Order A11-Registration Request (Lifetime, MEI)

b

c

Tregreq

A11-Registration Reply (Lifetime, accept) d

A11-Registration Update

e

Tregupd

A11-Registration Acknowledge f

A11-Registration Request (Lifetime=0)

g

Tregreq

A11-Registration Reply (Lifetime=0, accept)

8 9

h

Figure 4.1.3-1 HRPD to 1x Dormant Packet Data Session Handoff a. Upon transitioning to the 1x system, the MS/AT transmits an Origination message with DRS set to `0' and with layer 2 acknowledgment required over the access channel of the air interface to the target BS/PCF to request service. This message may contain the SID, NID and PZID corresponding to the source PCF from which the MS/AT is coming, if this capability is supported by the air interface. If available, these values are used to populate the PANID field of the A11-Registration Request message that the target BS/PCF sends to the PDSN. b. The target BS/PCF acknowledges receipt of the Origination message with a Base Station Acknowledgment Order to the MS/AT. c. The target BS/PCF sends an A11-Registration Request message to the PDSN. The A11-Registration Request message includes the MEI, the PANID of the source PCF and the CANID of the target PCF, within the CVSE. The target BS/PCF starts timer Tregreq. d. The A11-Registration Request message is validated and the PDSN accepts the connection by returning an A11-Registration Reply message with an accept indication and the Lifetime set to the configured Trp value. If the PDSN has data to send, it includes the Data Available Indicator within the CVSE. The A10 connection binding information at the PDSN is updated to point to the target BS/PCF. The target BS/ PCF stops timer Tregreq. If the PDSN responds to the target BS/PCF with the Data Available Indicator, the target BS/PCF establishes a traffic channel. In this case the remaining steps in this procedure are omitted. e. The PDSN initiates closure of the A10 connection with the source AN/PCF by sending an A11-Registration Update message. The PDSN starts timer Tregupd. 4-7

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7

May 2007

f.

The source AN/PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer Tregupd.

g. The source AN/PCF sends an A11-Registration Request message, with Lifetime set to zero, to the PDSN. The source AN/PCF starts timer Tregreq. h. The PDSN sends an A11-Registration Reply message to the source AN/PCF. The source AN/PCF closes the A10 connection for the MS/AT and stops timer Tregreq.

4-8

May 2007

A.S0007-A v3.0 HRPD IOS

1

4.2

MS/AT Terminated Voice Call During Active HRPD Packet Data Session

2 3

This section describes the call flows associated with an MS/AT terminated voice call during active HRPD packet data session. 4.2.1 MS/AT Terminated Voice Call During Active HRPD Data Packet (Intra-PDSN/Inter-PCF)

4 5 6 7

This scenario describes the call flow associated with an MS/AT terminated voice call while the MS/AT has an active HRPD packet data session. The HRPD packet data session transitions to the 1x system as a concurrent call service if the MS/AT has and selects this capability.

MS/ AT 1x BS PCF1 AN HRPD PCF2 PDSN time

HRPD active data session Page MS/AT stops transmitting to the AN A9-Release-A8 (Cause: Air link lost) a b c A11-Registration Request A11-Registration Reply d e f g h i j A9-Setup-A8 k A11-Registration Request (Lifetime, MEI) A11-Registration Reply (Lifetime, accept) l m n 1x active data session Connect Order A11-Registration Update o

Trel9

Tregreq

A9-Release-A8 Complete Page Response TCH setup AWI

Origination for concurrent service

TA8-setup

Tregreq

A9-Connect-A8

p q

Tregup

A11-Registration Ack A11-Registration Request (Lifetime=0) A11-Registration Reply (Lifetime=0, accept)

8 9

r s

Tregreq

t

Figure 4.2.1-1 Voice Call Termination During Active HRPD Packet Data Session (Inter-PCF)

4-9

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41

May 2007

a. The BS sends a Page message containing the MS/AT address over the paging channel. If the MS/AT accepts the Page message, the MS/AT stops transmitting to the AN. The MS/AT may ignore this Page message to continue the HRPD session. If the MS/AT ignores the message, the following steps are not performed. b. The AN does not receive any transmissions from the MS/AT for a sufficient amount of time. The AN considers the connection to be lost at this point. c. The AN sends an A9-Release-A8 message with cause value indicating `Air link lost', to PCF2 and starts timer Trel9. d. PCF2 sends an A11-Registration Request message containing an Active Stop accounting record to the PDSN and starts timer Tregreq. e. The PDSN sends an A11-Registration Reply message to PCF2. PCF2 stops timer Tregreq upon receipt of this message. f. PCF2 sends an A9-Release-A8 Complete message to the AN. The AN stops timer Trel9. The PCF should not attempt to re-page the MS/AT immediately upon receipt of the A9-Release-A8 message with cause value `Air link lost'.

g. The MS/AT sends a Page Response message to the BS. This step can occur any time after step c. h. The BS establishes a traffic channel. i. j. The BS sends an Alert with Info message to instruct the MS/AT to ring. The MS/AT and the 1x system set up the packet data session as a concurrent service if the MS/AT supports concurrent services and selects to transition the packet data session to the 1x system. Refer to [11], section 2.17.2.1 steps (a) to step (g).

k. The BS sends an A9-Setup-A8 message to PCF1 to establish the A8 connection and starts timer TA8setup. If the MS/AT has indicated the presence of data ready to send, the BS shall set the Data Ready Indicator to `1'; otherwise, the BS shall set the Data Ready Indicator to `0'. l. PCF1 sends an A11-Registration Request message to the PDSN to establish the A10 connection. PCF1 starts timer Tregreq.

m. The A11-Registration Request message is validated and the PDSN accepts the connection by returning an A11-Registration Reply message with an accept indication. PCF1 stops timer Tregreq. n. PCF1 sends an A9-Connect-A8 message after the completion of the A10 connection setup. The BS stops timer TA8-setup. o. At this point, the packet data session has successfully transitioned from the HRPD to the 1x system. p. The MS/AT sends a Connect Order message when the call is answered at the MS/AT. q. PDSN initiates closure of the A10 connection with PCF2 by sending an A11-Registration Update message. PDSN starts timer Tregupd. This step may occur immediately after step l. r. s. t. PCF2 responds with an A11-Registration Acknowledge message. The PDSN stops timer Tregupd. PCF2 sends an A11-Registration Request message, with Lifetime set to zero, to the PDSN. PCF2 starts timer Tregreq. The PDSN sends an A11-Registration Reply message to PCF2. PCF2 closes the A10 connection for the MS/AT and stops timer Tregreq.

4-10

May 2007

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5

4.2.2

AT Leaving During an Active HRPD Data Session

This section describes the call flow associated with an MS/AT leaving the HRPD session due to a terminated voice call or other reasons, while the MS/AT has an active packet data session. The scenario assumes that the AT does not initiate concurrent services prior to the detection of the loss of the HRPD radio link.

HRPD MS/ AT AN PCF2 BS 1x PCF1 PDSN time

HRPD active data session Page MS/AT stops transmitting to the AN A9-Release-A8 (Cause: Air link lost) a b c

Trel9

Tregreq

A11-Registration Request A11-Registration Reply

d e f g

A9-Release-A8 Complete Page Response TCH setup Alert with Info Connect Order

6 7

h i j

Figure 4.2.2-1 AT Leaving During an Active HRPD Data Session a. The BS sends a Page message containing the MS/AT address over the paging channel. If the MS/AT accepts the Page message, the MS/AT stops transmitting to the AN. The MS/AT may ignore this Page message to continue the HRPD session. If the MS/AT ignores the message, the following steps are not performed. b. The AN does not receive any transmissions from the MS/AT for a sufficient amount of time. The AN considers the connection to be lost at this point. c. The AN sends an A9-Release-A8 message with cause value indicating `Air link lost', to PCF2 and starts timer Trel9. d. PCF2 sends an A11-Registration Request message containing an Active Stop accounting record to the PDSN and starts timer Tregreq. e. The PDSN sends an A11-Registration Reply message to PCF2. PCF2 stops timer Tregreq upon receipt of this message. f. PCF2 sends an A9-Release-A8 Complete message to the AN. The AN stops timer Trel9.

8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

g. The MS/AT sends a Page Response message to the BS. This step can occur any time after step c. h. The BS establishes a traffic channel upon receipt of the Assignment Request message. i. j. The BS sends an Alert with Info message to instruct the MS/AT to ring. The MS/AT sends a Connect Order message when the call is answered at the MS/AT.

4-11

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3 4

4.2.3

MS/AT Terminated Voice Call During Active HRPD Packet Data Session (Intra-PCF)

This scenario describes the call flow associated with an MS/AT terminated voice call while the MS/AT has an active HRPD packet data session. The HRPD packet data session transitions to the 1x system as a concurrent call service if the MS/AT has and selects this capability.

MS/ AT 1x BS AN HRPD PCF PDSN time HRPD Active Data Session Page MS/AT stops transmitting to the AN X A9-Release-A8 (Cause: Air Link Lost) a b c

Trel9

Tregreq

A9-Release-A8 Complete

A11-Registration Request A11 Registration Reply

d e f g h i j

Page Response TCH Setup Alert with Info Origination for Concurrent Service A9-Setup-A8

k

TA8-setup

A9-Connect-A8 1x Active Data Session

Tregreq

A11-Registration Request A11-Registration Reply

l m n o

Connect Order

5 6

p

Figure 4.2.3-1 Voice Call Termination During Active HRPD Packet Data Session (Intra-PCF) a. The BS sends a Page message containing the MS/AT address over the paging channel. If the MS/AT accepts the Page message, the MS/AT stops transmitting to the AN. The MS/AT may ignore this Page message to continue the HRPD session. If the MS/AT ignores the message, the following steps are not performed. b. The AN does not receive any transmissions from the MS/AT for a sufficient amount of time. The AN considers the connection to be lost at this point. c. The AN sends an A9-Release-A8 message with cause value indicating `Air link lost', to the PCF and starts timer Trel9. d. The PCF sends an A11-Registration Request message containing an Active Stop accounting record to the PDSN and starts timer Tregreq.

7 8 9 10 11 12 13 14 15 16

4-12

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

A.S0007-A v3.0 HRPD IOS

e. The PDSN sends an A11-Registration Reply message to the PCF. The PCF stops the timer Tregreq upon receipt of the message. f. Upon receipt of the A9-Release-A8 message, the PCF sends an A9-Release-A8 Complete message to the AN. The AN stops timer Trel9.

g. The MS/AT sends a Page Response message to the BS. This step can occur any time after step c. h. The BS establishes a traffic channel. i. j. The BS sends an Alert with Info message to instruct the MS/AT to ring. The MS/AT and 1x system set up the packet data session as a concurrent service if the MS/AT supports concurrent services and selects to transition the packet data session to the 1x system. Refer to [11], section 2.17.2.1 steps (a) to step (g).

k. The BS sends an A9-Setup-A8 message to the PCF to establish the A8 connection and starts timer TA8-setup. If the MS/AT has indicated the presence of data ready to send, the BS shall set the Data Ready Indicator to `1'; otherwise, the BS shall set the Data Ready Indicator to `0'. l. The PCF sends an A11-Registration Request message containing an Active Start accounting record to the PDSN and starts timer Tregreq.

m. The PDSN sends an A11-Registration Reply message to the PCF. The PCF stops the timer Tregreq upon receipt of the message. n. The PCF sends an A9-Connect-A8 message to the BS. The BS stops timer TA8-setup. o. At this point, the packet data session has successfully transitioned from the HRPD system to the 1x system. p. The MS/AT sends a Connect Order message when the call is answered at the MS/AT.

4-13

A.S0007-A v3.0 HRPD IOS

May 2007

1

4.3

1x to HRPD Active Packet Data Session Transition

2 3 4 5 6 7 8 9 10 11 12

This section describes how an active packet data session on a 1x system can be transitioned to an HRPD system. This transition is accomplished by means of a dormant handoff of the packet data session. In this scenario, it is assumed that the MS/AT has already established an HRPD session, however it does not have a connection established. Transition of the active 1x packet data session occurs via the dormant state. The transition from 1x active to dormant occurs according to [11] 2.14.7.3, MS Initiated Call Release to Dormant State. The dormant handoff from 1x to HRPD occurs according to section 4.1.1 or 4.1.2 (1x to HRPD Dormant Packet Data Session Handoff - Existing or New HRPD Session) as appropriate. Finally, the MS/AT transitions from dormant to active on HRPD according to section 3.3.2, AT Initiated Call Re-activation from Dormant State (Existing HRPD Session).

4-14

May 2007

A.S0007-A v3.0 HRPD IOS

1

4.4

Status Management Supported by Feature Invocation

2

This scenario describes the call flow associated with status management using feature invocation.

MS/AT

BS

1x

MSC

HRPD

AN

time a

Origination (Feature Code) Mobile Originating Call Setup MSC Initiated Call Clearing

b c

Mobile Initiated HRPD Connection Setup

d

Mobile Initiated HRPD Connection Release

e

Origination (Feature Code) Mobile Originating Call Setup

f g

MSC Initiated Call Clearing

h

3 4

Figure 4.4-1

Terminal Based Status Management (Using Feature Invocation)

5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

a. The MS/AT sends an Origination message, including the feature code as the called number, to the BS before the MS/AT initiates an HRPD connection. This feature code indicates that the MSC should activate a feature (e.g., do not disturb). b. The BS and the MSC setup the call. From the feature code, the MSC knows not to page the MS/AT for a voice call. Refer to [11], section 2.2.2.1, Mobile Origination. c. The BS and the MSC clear the call. Refer to [11], section 2.3.5.3, Call Clear Initiated by MSC. d. The MS/AT starts communication on the HRPD session. Refer to section 3.3.2, AT Initiated Call Reactivation from Dormant State (Existing HRPD Session). e. The MS/AT terminates communication on the HRPD session when the HRPD session goes dormant or inactive. Refer to section 3.5.2, HRPD Session Release - Initiated by the AT (No Connection Established). f. The MS/AT sends an Origination message, including the feature code as the calling number, to the BS when the MS/AT ends the HRPD connection. This feature code indicates that the MSC should deactivate the feature activated in step a.

g. The BS and the MSC setup the call. From the feature code, the MSC know it may page the MS/AT for a voice call. Refer to [11], section 2.2.2.1, Mobile Origination. h. The BS and the MSC clear the call. Refer to [11], section 2.3.5.3, Call Clear Initiated by MSC.

4-15

A.S0007-A v3.0 HRPD IOS

1 2

May 2007 No text.

4-16

May 2007

1

A.S0007-A v3.0 HRPD IOS

5 Messages, Information Elements and Timer Definitions

5.1

5.1.1 5.1.1.1

2

Message Definitions

A13 Message Definitions A13-Session Information Request

3

4 5 6

This message is sent from the target PCF to the source PCF to request session control information for a particular AT. Information Element A13 Message Type UATI 128 Security Layer Packet Sector ID (target) Section Reference Element Direction 5.2.1.2 5.2.1.3 5.2.1.4 5.2.1.5 Target PCF Source PCF Target PCF Source PCF Target PCF Source PCF Target PCF Source PCF O

a

Type M R R R O O

7 8

a. Refer to section 2.4 for information about this information element. The following table shows the bitmap layout for the A13-Session Information Request message. 7 6 (MSB) 5 4 3 2 1 0 Octet 1 1 2 3 4 (LSB) (MSB) Security Layer Packet: A13 Element Identifier = [02H] Length = [variable] Security Layer Packet 18 1 2 3 4 (LSB) (MSB) Sector ID: A13 Element Identifier = [03H] Length = [10H] Sector ID = <any value> n 1 2 3 4 (LSB) 18 A13 Message Type = [01H] Length = [10H] UATI = <any value>

UATI 128: A13 Element Identifier = [01H]

9

5-1

A.S0007-A v3.0 HRPD IOS

May 2007

1 2 3

5.1.1.2

A13-Session Information Response

This message is sent from the source PCF to the target PCF and includes the requested session control information. Information Element A13 Message Type UATI 128 Mobile Identity (MN ID) PDSN IP Address Access Network Identifiers Session State Information Record Section Reference 5.2.1.2 5.2.1.3 5.2.1.7 5.2.1.8 5.2.1.9 5.2.1.10 Element Direction Source PCF Target PCF Source PCF Target PCF Source PCF Target PCF Source PCF Target PCF Source PCF Target PCF Source PCF Target PCF O O O

a c

Type M R C C C R

Oc

c

Ob

4 5 6 7 8 9

a. The UATI is set to the same value as the UATI received in the A13-Session Information Request message. b. Multiple copies of this information element may be included. If an attribute is not contained in the Session State Information Record, the target AN shall assume that the missing attribute(s) have the default values (specified for each attribute in each protocol). c. This IE is included if the information is available at the source PCF. The following table shows the bitmap layout for the A13-Session Information Response message. 7 6 (MSB) 5 4 3 2 1 0 Octet 1 1 2 3 4 (LSB) Mobile Identity (MN ID): A13 Element Identifier = [05H] Length = [06H - 08H] (10 - 15 digits)

Identity Digit 1 = [0H-9H] (BCD) Odd/even Indicator = [1,0] Type of Identity = [110] (MN ID)

10

A13 Message Type = [04H] Length = [10H] UATI = <any value>

UATI 128: A13 Element Identifier = [01H]

18 1 2

3

Identity Digit 3 = [0H-9H] (BCD) Identity Digit N+1 = [0H-9H] (BCD) = [1111] (if even number of digits) (MSB)

Identity Digit 2 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD)

4

k Identity Digit N+2 = [0H-9H] (BCD) k+1 1 2 3 PDSN IP Address: A13 Element Identifier = [06H] Length = [04H] PDSN IP Address 5-2

May 2007 7 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet 4 5 (LSB) Access Network Identifiers: A13 Element Identifier = [07H] Type = 01H Length = [05H] 6 1 2 3 4 (LSB) 5 6 (LSB) 7 8 1 2 (LSB) 3 4 (LSB) n (LSB)

Reserved

(MSB)

SID NID PZID Length = [variable] Session State Information Record

(MSB) (MSB) (MSB) (MSB)

Session State Information Record: A13 Element Identifier = [08H]

1 2 3

5.1.1.3

A13-Session Information Confirm

This message is sent from the target PCF to the source PCF to indicate that the target PCF has successfully received the session control information for the requested AT. Information Element A13 Message Type UATI 128 Section Reference Element Direction 5.2.1.2 5.2.1.3 Target PCF Source PCF Target PCF Source PCF O

a

Type M R

4 5 6

a. The UATI is set to the same value as the UATI sent in the A13-Session Information Request message. The following table shows the bitmap layout for the A13-Session Information Confirm message. 7 6 (MSB) 5 4 3 2 1 0 Octet 1 1 2 3 4 (LSB) 18 A13 Message Type = [02H] Length = [10H] UATI = <any value>

UATI 128: A13 Element Identifier = [01H]

7 8 9

5.1.1.4

A13-Session Information Reject

This message is sent from the source PCF to the target PCF to indicate that the request for session control information has been denied. 5-3

A.S0007-A v3.0 HRPD IOS Information Element A13 Message Type UATI 128 Cause

1 2 3

May 2007 Section Reference 5.2.1.2 5.2.1.3 5.2.1.6 Element Direction Source PCF Target PCF Source PCF Target PCF Source PCF Target PCF O

a

Type M R R O

a. The UATI is set to the same value as the UATI received in the in A13-Session Information Request message. The following table shows the bitmap layout for the A13-Session Information Reject message. 7 6 (MSB) 5 4 3 2 1 0 Octet 1 1 2 3 4 (LSB) Cause: A13 Element Identifier = [04H] Length = [01H] Cause Value = [ 01H (Protocol subtype not recognized), 02H (Protocol subtype attribute(s) not recognized), 03H (Protocol subtype attribute(s) missing), 04H (Requested session not found), 05H (Requested session not authentic)] 18 1 2 3 A13 Message Type = [03H] Length = [10H] UATI = <any value>

UATI 128: A13 Element Identifier = [01H]

5-4

May 2007

A.S0007-A v3.0 HRPD IOS

1

5.1.2 5.1.2.1

A14 Message Definitions A14-UATI Request

2 3

This message is sent from the AN to the PCF to request a UATI for a particular AT. Information Element A14 Message Type ATI (RATI / UATI32) (current) Correlation ID Sector ID Security Layer Packet System Time Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.5 5.2.2.10 5.2.2.17 Element Direction AN PCF AN PCF AN PCF AN PCF AN PCF AN PCF Oa O

b

Type M R C R C C

Oc,d O O

e

4 5 6 7 8 9 10 11

a. UATI32 is included when UATI has already been assigned to the AT. b. If this information element is included in this message, its value shall be returned in the corresponding information element in the A14-UATI Assignment message sent in response to this message. c. RATI is included when this message is sent for initial UATI assignment. d. This information element is used for identifying in which sector a registration occurs with the RATI. In the case of a dormant handoff across a subnet boundary, this information element is used to identify the sector from which the AT registered. e. This information element is used to validate the security layer packet included in this message. The following table shows the bitmap layout for the A14-UATI Request message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI32), 3H (RATI)] (LSB) 3 A14 Message Type = [27H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] IF (ATI Type = 2 H), UATI32 Entry { 1: (MSB) (MSB) UATIColorCode = <any value> UATI024 = <any value> (LSB) } OR IF (ATI Type = 3 H), RATI Entry { 1: (MSB) RATI = <any value> 4 5 6 (LSB) } RATI Entry Correlation ID: A14 Element Identifier = [13H] 5-5 1 7 4 5 6 7

12

A.S0007-A v3.0 HRPD IOS 7 (MSB) 6 5 4 3 2 1 0

May 2007 Octet 2 3 4 5 (LSB) Sector ID: A14 Element Identifier = [88H] Length = [11H] (LSB) 6 1 2 3 4 5 (LSB) 19 1 2 3 4 (LSB) n 1 2 3 4 (LSB) 10

Length = [04H] Correlation value = <any value>

(MSB) (MSB)

SectorID Discriminator = [01H (SectorID128)] Sector ID = <any value>

(MSB)

Security Layer Packet: A14 Element Identifier = [89H] Length = [variable] Security Layer Packet

(MSB)

System Time: A14 Element Identifier = [8CH] Length = [08H] CDMA System Time = <any value>

1

2 3

5.1.2.2

A14-UATI Assignment

This message is sent from the PCF to the AN to assign a UATI for a particular AT. Information Element A14 Message Type ATI (RATI / UATI32) (current) Correlation ID Sector ID Message Sequence ATI(UATI 32 / UATI128) (new) UATI Color Code (new) UATI Subnet Mask (new) Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.5 5.2.2.11 5.2.2.3 5.2.2.18 5.2.2.14 Element Direction PCF AN PCF AN PCF AN PCF AN PCF AN PCF AN PCF AN PCF AN O Oc O

a,

Type M

a,b

R C C R R C C

O O O

d e

O

5-6

May 2007 Information Element Upper Old UATI Length

1 2 3 4 5 6 7 8 9 10 11

A.S0007-A v3.0 HRPD IOS Section Reference 5.2.2.12 Element Direction PCF AN Type Of C

a. This information element shall be set to the same value received in the A14-UATI Request message. b. UATI32 is included when UATI has already been assigned to the AT. c. This information element shall be included if it was also included in the A14-UATI Request message and shall be set to the value received in that message. Otherwise, this information element is optionally included. If included, its value shall be returned in the corresponding information element in the A14-UATI Complete message sent in response to this message. d. This information element is included when the ATI is a UATI128. e. This information element is always included unless the AN is using a default UATI subnet mask. Refer to [10]. f. This information element is included if the PCF requires the old UATI. This information element contains the length of the old UATI.

12

The following table shows the bitmap layout for the A14-UATI Assignment message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI32), 3H (RATI)] (LSB) 3 A14 Message Type = [28H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] IF (ATI Type = 2 H), UATI32 Entry { 1: (MSB) (MSB) UATIColorCode = <any value> UATI024 = <any value> (LSB) } OR IF (ATI Type = 3 H), RATI Entry { 1: (MSB) RATI = <any value> 4 5 6 (LSB) } RATI Entry (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation value = <any value> 1 2 3 4 5 (LSB) Sector ID: A14 Element Identifier = [88H] Length = [11H] 5-7 6 1 2 7 4 5 6 7

A.S0007-A v3.0 HRPD IOS 7 (MSB) (MSB) 6 5 4 3 2 1 0 (LSB)

May 2007 Octet 3 4 5 (LSB) 19 1 2 (LSB) 3 1 2 3

SectorID Discriminator = [01H (SectorID128)] Sector ID = <any value>

(MSB)

Message Sequence: A14 Element Identifier = [83H] Length = [01H] Message Sequence ATI: A14 Element Identifier = [80H] Length = [05H, 11H] ATI Type = [2H (UATI 32) 4H (UATI128) ] (LSB)

History Ind = [1H (Newly)] IF (ATI Type = 2 H), UATI32 Entry { 1: (MSB) (MSB)

UATIColorCode = <any value> UATI024 = <any value>

4 5 6

(LSB) } OR IF (ATI Type = 4 H), UATI128 Entry { 1: (MSB) UATI104

7 4 5

(LSB) (MSB) UATI024 = <any value> (LSB) } UATI128 Entry (MSB) (MSB) UATI Color Code: A14 Element Identifier = [8DH] Length = [01H] UATI Color Code UATI Subnet Mask: A14 Element Identifier = [86H] Length = [01H] UATI Subnet Mask Upper Old UATI Length: A14 Element Identifier = [84H] Length = [01H] Reserved = [0000] Upper Old UATI Length = <any value> (LSB) (LSB)

16 17 18 19 1 2 3 1 2 3 1 2 3

5-8

May 2007

1 2 3

A.S0007-A v3.0 HRPD IOS A14-UATI Complete

5.1.2.3

This message is sent from the AN to the PCF to notify the PCF that UATI assignment completed successfully. Information Element A14 Message Type ATI (UATI 32) (updated) Correlation ID Message Sequence Upper Old UATI Length Upper Old UATI Sector ID Security Layer Packet System Time Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.11 5.2.2.12 5.2.2.13 5.2.2.5 5.2.2.10 5.2.2.17 Element Direction AN PCF AN PCF AN PCF AN PCF AN PCF AN PCF AN PCF AN PCF AN PCF O O O

a b

Type M R C R C C C C C

O

b

Ob,c O

d

Oe O

f

4 5 6 7 8 9 10 11 12 13 14

a. This information element shall be set to the UATI value assigned in the A14-UATI Assignment message. b. This information element shall only be included if it was also included in the A14-UATI Assignment message. This information element shall be set to the value received in that message. c. This information element shall only be included if it was also included in the A14-UATI Assignment message. This information element shall be set to the value of the old UATI. d. This information element shall be set to the same value received in the A14-UATI Assignment message. e. The AN shall include this information element if the security layer packet from the AT has to be validated and the AN cannot validate it. Refer to [10]. f. This information element is used to validate the security layer packet included in this message.

15

The following table shows the bitmap layout for the A14-UATI Complete message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation value = <any value> 7 1 2 3 4 5 5-9 A14 Message Type = [29H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

A.S0007-A v3.0 HRPD IOS 7 6 (MSB) 5 4 3 2 1 0 (LSB) Message Sequence: A14 Element Identifier = [83H] Length = [01H] Message Sequence Upper Old UATI Length: A14 Element Identifier = [84H] Length = [01H] Reserved = [0000] (MSB) Upper Old UATI Length = <any value> (LSB)

May 2007 Octet 6 1 2 3 1 2 3 1 2 3 (LSB) Sector ID: A14 Element Identifier = [88H] Length = [11H] (LSB) n 1 2 3 4 5 (LSB) 19 1 2 3 4 (LSB) n 1 2 3 4 (LSB) 10

Upper Old UATI: A14 Element Identifier = [85H] Length = [variable] Upper Old UATI

(MSB) (MSB)

SectorID Discriminator = [01H (SectorID128)] Sector ID = <any value>

(MSB)

Security Layer Packet: A14 Element Identifier = [89H] Length = [variable] Security Layer Packet

(MSB)

System Time: A14 Element Identifier = [8CH] Length = [08H] CDMA System Time = <any value>

1 2

5.1.2.4

A14-UATI Complete Ack

This message is sent from the PCF to the AN to acknowledge that A14-UATI Complete message. Information Element A14 Message Type ATI (UATI 32) (updated) Section Reference 5.2.2.2 5.2.2.3 5-10 Element Direction PCF AN PCF AN O

a

Type M R

May 2007 Information Element Correlation ID

1 2 3 4

A.S0007-A v3.0 HRPD IOS Section Reference 5.2.2.4 Element Direction PCF AN Type Ob C

a. This information element shall be set to the UATI value assigned in the A14-UATI Complete message. b. This information element shall only be included if it was also included in the A14-UATI Complete message. This information element shall be set to the value received in that message. The following table shows the bitmap layout for the A14-UATI Complete Ack message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation value = <any value> 7 1 2 3 4 5 (LSB) 6 A14 Message Type = [2AH] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

5

6 7

5.1.2.5

A14-UATI Assignment Failure

This message is sent from the PCF to the AN to indicate assignment failure of the UATI to the AT. Information Element A14 Message Type ATI (RATI / UATI32) (current) Correlation ID Cause Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.9 Element Direction PCF AN PCF AN PCF AN PCF AN O

c

Type M Oa,b O R C R

8 9 10 11 12

a. RATI is included when the received A14-UATI Request message includes the RATI. b. UATI32 is included when the received A14-UATI Request message includes the UATI32 (in the case of dormant handoff.). c. This information element shall only be included if it was also included in the A14-UATI Assignment message. This information element shall be set to the value received in that message. The following table shows the bitmap layout for the A14-UATI Assignment Failure message. 7 6 5 4 3 2 1 0 Octet 1 A14 Message Type = [2BH] 5-11

13

A.S0007-A v3.0 HRPD IOS 7 6 5 4 3 2 1 0

May 2007 Octet 1 2 ATI Type = [2H (UATI32), 3H (RATI)] (LSB) 3

ATI: A14 Element Identifier = [80H] Length = [05H]

History Ind = [0H (Current)] IF (ATI Type = 2 H), UATI32 Entry { 1: (MSB) (MSB)

UATIColorCode = <any value> UATI024 = <any value>

4 5 6

(LSB) } OR IF (ATI Type = 3 H), RATI Entry { 1: (MSB) RATI = <any value>

7 4 5 6

(LSB) } RATI Entry (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation value = <any value>

7 1 2 3 4 5

(LSB) Cause: A14 Element Identifier = [04H] Length = [01H] Cause Value = [05H (Session unreachable), 06H (All session resources busy)]

1 2 3 4 5

6 1 2 3

5.1.2.6

A14-General Update

This message is sent from the AN to the PCF to indicate the AT's location information. In addition, this message includes the PANID if the location update procedure is performed, Session State Information if XonRequest or XoffResponse is received, or the Keep Alive Indicator (set to `1') if the KeepAliveRequest message is received. Information Element A14 Message Type ATI (UATI 32) Correlation ID Sector ID Security Layer Packet System Time Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.5 5.2.2.10 5.2.2.17 Element Direction AN PCF AN PCF AN PCF AN PCF AN PCF AN PCF O Oa O Ob O

c

Type M R C R C C

5-12

May 2007 Information Element Access Network Identifiers Session State Information Record A14 Indicators

1 2 3 4 5 6 7 8 9 10 11 12 13

A.S0007-A v3.0 HRPD IOS Section Reference 5.2.2.16 5.2.2.7 5.2.2.8 Element Direction AN PCF AN PCF AN PCF O O Type

d e f

C C C

O

a. If this information element is included in this message, its value shall be returned in the corresponding information element in the A14-General Update Complete message sent in response to this message. b. The AN shall include this information element if the security layer packet from the AT has to be validated and the AN cannot validate it. Refer to [10]. c. This information element is used to validate the security layer packet included in this message. d. The Access Network Identifiers (PANID) are included if the AN retrieved them from the AT. e. This information element is included when the AN receives a message requiring state changes. Only Session State Information Record that have changed are included in this record. Multiple copies of this information element may be included. f. This information element is included when the AN receives a KeepAliveRequest message. If this information element is not included, the PCF shall assume that all bits in this information element are set to `0'.

14

The following table shows the bitmap layout for the A14-General Update message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) (MSB) (MSB) Sector ID : A14 Element Identifier = [88H] Length = [11H] SectorID Discriminator = [01H (SectorID128)] Sector ID = <any value> (LSB) 6 1 2 3 4 5 (LSB) 5-13 19 (LSB) A14 Message Type = [20H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

A.S0007-A v3.0 HRPD IOS 7 (MSB) 6 5 4 3 2 1 0

May 2007 Octet 1 2 3 4 (LSB) n 1 2 3 4 (LSB) 10 1 2 3 (LSB) 4 5 (LSB) 6 7 1 2 (LSB) 3 4 (LSB) n 1 2 Paging Type Indicator =[0] A15 AuthentPaging ication Inhibited Required =[0] =[0] 3 (LSB)

Security Layer Packet: A14 Element Identifier = [89H] Length = [variable] Security Layer Packet

(MSB)

System Time: A14 Element Identifier = [8CH] Length = [08H] CDMA System Time = <any value>

Access Network Identifiers : A14 Element Identifier = [20H] Length = [05H] SID = <any value> NID = <any value> PZID = <any value> Length = [variable] Session State Information Record

Reserved (MSB) (MSB) (MSB) (MSB) (MSB)

Session State Information Record: A14 Element Identifier = [8AH]

A14 Indicators: A14 Element Identifier = [82H] Length = [01H] Keep Alive Indicator =[0, 1] Data Ready Indicator =[0]

Reserved = [000]

1 2

5.1.2.7

A14-General Update Complete

This message is sent from the PCF to the AN to respond to the A14-General Update message. Information Element A14 Message Type ATI (UATI 32) Correlation ID Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 Element Direction PCF AN PCF AN PCF AN O Oa Type M R C

5-14

May 2007 Information Element Cause

1 2 3 4

A.S0007-A v3.0 HRPD IOS Section Reference 5.2.2.9 Element Direction PCF AN O Type

b

C

a. This information element shall only be included if it was also included in the A14-General Update message. This information element shall be set to the value received in that message. b. This information element is used to indicate a failure situation if the session information is not reachable. When the AN receives this information element, it performs the session release procedure. The following table shows the bitmap layout for the A14-General Update Complete message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) Cause: A14 Element Identifier = [04H] Length = [01H] Cause Value = [05H (Session unreachable), 09H (Invalid session information)] 6 1 2 3 (LSB) A14 Message Type = [21H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

5

6 7

5.1.2.8

A14-Authentication Command

This message is sent from the PCF to the AN to start the terminal authentication of an active AT. Information Element A14 Message Type ATI (UATI 32) Correlation ID Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 Element Direction PCF AN PCF AN PCF AN O O

a

Type M R C

8 9

a. If this information element is included in this message, its value shall be returned in the corresponding information element in the A14-Authentication Request message sent in response to this message. The following table shows the bitmap layout for the A14-Authentication Command message. 7 6 5 4 3 2 1 0 Octet 1 A14 Message Type = [22H] 5-15

10

A.S0007-A v3.0 HRPD IOS 7 6 5 4 3 2 1 0

May 2007 Octet 1 2 3 4 5 6 (LSB) 7 1 2 3 4 5 (LSB) 6 (LSB)

ATI: A14 Element Identifier = [80H] Length = [05H] ATI Type = [2H (UATI 32)]

History Ind = [0H (Current)] (MSB) (MSB)

UATIColorCode = <any value> UATI024 = <any value>

(MSB)

Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value>

1 2 3

5.1.2.9

A14-Authentication Request

This message is sent from the AN to the PCF to indicate the resource information (i.e. IP address and GRE key) at the AN. Information Element A14 Message Type ATI (UATI 32) Correlation ID Ax Traffic ID Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.15 Element Direction AN PCF AN PCF AN PCF AN PCF O O

a

Type M R C R

O

4 5 6 7

a. This information element shall be included if it was also included in the A14-Authentication Command message and shall be set to the value received in that message. Otherwise, this information element is optionally included. If included, its value shall be returned in the corresponding information element in the A14-Authentication Response message sent in response to this message. The following table shows the bitmap layout for the A14-Authentication Request message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 (LSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] 5-16 7 1 2 (LSB) A14 Message Type = [23H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

8

May 2007 7 (MSB) 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet 3 4 5 (LSB) Ax Traffic ID: A14 Element Identifier = [87H] Length = [0CH] Ax transport protocol stack = [01H] (GRE/IP) 6 1 2 3 4 (LSB) 5 6 7 8 (LSB) Address Type = [01H] (IPv4) 9 10 11 12 13 (LSB) 14

Correlation Value = <any value>

(MSB) (MSB)

Protocol Type = [88 81H] (Unstructured byte stream) Key = <any value>

(MSB)

IP Address = <any value>

1 2 3

5.1.2.10

A14-Authentication Response

This message is sent from the PCF to the AN to indicate the resource information (i.e. IP address and GRE key) at the PCF. Information Element A14 Message Type ATI (UATI 32) Correlation ID Ax Traffic ID Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.15 Element Direction PCF AN PCF AN PCF AN PCF AN O Oa O Type M R C R

4 5

a. This information element shall only be included if it was also included in the A14-Authentication Request message. This information element shall be set to the value received in that message. The following table shows the bitmap layout for the A14-Authentication Response message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 5-17 (LSB) A14 Message Type = [24H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

6

A.S0007-A v3.0 HRPD IOS 7 6 (MSB) 5 4 3 2 1 0 (LSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value>

May 2007 Octet 7 1 2 3 4 5 (LSB) 6 1 2 3 4 (LSB) 5 6 7 8 (LSB) Address Type = [01H] (IPv4) 9 10 11 12 13 (LSB) 14

Ax Traffic ID: A14 Element Identifier = [87H] Length = [0CH] Ax transport protocol stack = [01H] (GRE/IP)

(MSB) (MSB)

Protocol Type = [88 81H] (Unstructured byte stream) Key = <any value>

(MSB)

IP Address = <any value>

1 2

5.1.2.11

A14-Authentication Completed

This message is sent from the PCF to AN to indicate the result of the terminal authentication. Information Element A14 Message Type ATI (UATI 32) Correlation ID Cause A14 Indicators Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.9 5.2.2.8 Element Direction PCF AN PCF AN PCF AN PCF AN PCF AN O Oa O O

b

Type M R C R C

3 4 5 6 7

a. If this information element is included in this message, its value shall be returned in the corresponding information element in the A14-Authentication Completed Ack message sent in response to this message. b. This information element shall be included only if the PCF has data to send when this message is sent. The following table shows the bitmap layout for the A14-Authentication Completed message. 7 6 5 4 3 2 1 0 Octet 1 A14 Message Type = [25H] 5-18

8

May 2007 7 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet 1 2 3 4 5 6 (LSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) Cause: A14 Element Identifier = [04H] Length = [01H] Cause Value = [ 03H (Authentication succeeded), 04H (Authentication failure), 07H (PCF resource unavailable), 08H (AN-AAA unreachable)] Length = [01H] 6 1 2 3 (LSB)

ATI: A14 Element Identifier = [80H] Length = [05H] ATI Type = [2H (UATI 32)]

History Ind = [0H (Current)] (MSB) (MSB)

UATIColorCode = <any value> UATI024 = <any value>

(MSB)

A14 Indicators: A14 Element Identifier = [82H] Keep Alive Indicator =[0] Data Ready Indicator =[0,1] Paging Type Indicator =[0] A15 AuthentPaging ication Inhibited Required =[0] =[0]

1 2 3

Reserved = [000]

1 2 3

5.1.2.12

A14-Authentication Completed Ack

This message is sent from the AN to the PCF to acknowledge the A14-Authentication Completed message. Information Element A14 Message Type ATI (UATI 32) Correlation ID Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 Element Direction AN PCF AN PCF AN PCF O O

a

Type M R C

4 5

a. This information element shall only be included if it was also included in the A14-Authentication Completed message. This information element shall be set to the value received in that message. The following table shows the bitmap layout for the A14-Authentication Completed Ack message. 7 6 5 4 3 2 1 0 Octet 1 1 A14 Message Type = [26H] ATI: A14 Element Identifier = [80H] 5-19

6

A.S0007-A v3.0 HRPD IOS 7 6 5 4 3 2 1 0

May 2007 Octet 2 3 4 5 6 (LSB) 7 1 2 3 4 5 (LSB) 6 (LSB)

Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

(MSB)

Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value>

1 2

5.1.2.13

A14-Authentication Failure

This message is sent from the AN to the PCF to indicate a failure condition in the AN. Information Element A14 Message Type ATI (UATI 32) Correlation ID Cause Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.9 Element Direction AN PCF AN PCF AN PCF AN PCF O O

a

Type M R C R

O

3 4 5 6

a. If this information element is included in this message, its value shall be returned in the corresponding information element in the A14-Authentication Failure Ack message sent in response to this message. The following table shows the bitmap layout for the A14-Authentication Failure message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI 32)] (LSB) 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 5-20 A14 Message Type = [35H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) UATIColorCode = <any value> UATI024 = <any value>

May 2007 7 6 5 4 3 2 1 0 (LSB) Cause: A14 Element Identifier = [04H] Length = [01H] Cause Value = [0AH (AN resource unavailable), 0BH (Equipment failure), 0CH (Air link lost)]

1 2

A.S0007-A v3.0 HRPD IOS Octet 6 1 2 3

5.1.2.14

A14-Authentication Failure Ack

This message is sent from the PCF to the AN to acknowledge an A14-Authentication Failure message. Information Element A14 Message Type ATI (UATI 32) Correlation ID Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 Element Direction PCF AN PCF AN PCF AN O O

a

Type M R C

3 4 5

a. This information element shall only be included if it was also included in the A14-Authentication Failure message. This information element shall be set to the value received in that message. The following table shows the bitmap layout for the A14-Authentication Failure Ack message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI 32)] (LSB) 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) 6 A14 Message Type = [36H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) UATIColorCode = <any value> UATI024 = <any value>

6 7 8

5.1.2.15

A14-Session Release Command

This message is sent from the PCF to the AN to request that the AN initiate the HRPD session release procedure. Information Element A14 Message Type ATI (UATI 32) Section Reference 5.2.2.2 5.2.2.3 5-21 Element Direction PCF AN PCF AN O Type M R

A.S0007-A v3.0 HRPD IOS Information Element Correlation ID Sector ID (Registered Sector) Sector ID List Cause Session State Information Record

1 2 3 4 5 6 7

May 2007 Section Reference 5.2.2.4 5.2.2.5 5.2.2.6 5.2.2.9 5.2.2.7 Element Direction PCF AN PCF AN PCF AN PCF AN PCF AN O O Type

a

C R C C C

b

Ob O Oc

a. If this information element is included in this message, its value shall be returned in the corresponding information element in the A14-Session Release message sent in response to this message. b. This information element is included if the PCF indicates an area in which the AN is to send the SessionClose message. c. This information element is included when the AN does not have the session state information for the AT (e.g., when the AT does not have an active connection). Multiple copies of this information element may be included. The following table shows the bitmap layout for the A14-Session Release Command message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) (MSB) (MSB) Sector ID: A14 Element Identifier = [88H] Length = [11H] SectorID Discriminator = [01H (SectorID128)] Sector ID = <any value> (LSB) 6 1 2 3 4 5 (LSB) Sector ID List: A14 Element Identifier = [81H] Length = [variable] 5-22 19 1 2 (LSB) A14 Message Type = [34H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

8

May 2007 7 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet 3

SectorID Discriminator = [01H (SectorID128), 02H (SectorID32)] IF (SectorID Discriminator = 01 H), SectorID128 Entry { 1+: (MSB) SectorID128 = <any value>

k k+1 (LSB) k+15 k k+1 k+2 (LSB) k+3 1 2 3

} OR IF (SectorID Discriminator = 02 H), SectorID32 Entry { 1+: (MSB) (MSB) ColorCode = <any value> SectorID24 = <any value> (LSB)

} SectorID32 Entry Cause: A14 Element Identifier = [04H] Length = [01H] Cause Value = [04H (Authentication failure), 06H (All session resources busy), 0DH (Protocol error), 10H (Session lost), 14H (Normal Release)] (MSB) (MSB) Session State Information Record: A14 Element Identifier = [8AH] Length = [variable] (LSB) Session State Information Record (LSB)

1 2 3

1 2 3 4 n

5.1.2.16

A14-Session Release

The A14-Session Release message is sent from the AN to the PCF to request the PCF to release the associated dedicated resource. Information Element A14 Message Type ATI (UATI 32) Correlation ID Sector ID Cause Security Layer Packet Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.5 5.2.2.9 5.2.2.10 Element Direction AN PCF AN PCF AN PCF AN PCF AN PCF AN PCF O Oa O O Ob Type M R C R R C

5-23

A.S0007-A v3.0 HRPD IOS Information Element System Time

1 2 3 4 5 6 7 8

May 2007 Section Reference 5.2.2.17 Element Direction AN PCF Type C Oc

a. This information element shall be included if it was also included in the A14-Session Release Command message and shall be set to the value received in that message. Otherwise, this information element is optionally included. If included, its value shall be returned in the corresponding information element in the A14-Session Release Complete message sent in response to this message. b. The AN shall include this information element if the security layer packet from the AT has to be validated and the AN cannot validate it. Refer to [10]. c. This information element is used to validate the security layer packet included in this message. The following table shows the bitmap layout for the A14-Session Release message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI 32)] (LSB) 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) (MSB) (MSB) Sector ID: A14 Element Identifier = [88H] Length = [11H] SectorID Discriminator = [01H (SectorID128)] Sector ID = <any value> (LSB) 6 1 2 3 4 5 (LSB) Cause: A1 Element Identifier = [04H] 19 1 2 3

A14 Message Type = [2CH] Length = [05H]

ATI (UATI 32): A14 Element Identifier = [80H]

History Ind = [0H (Current)] (MSB) (MSB)

UATIColorCode = <any value> UATI024 = <any value>

Length = [01H] Cause Value= [0DH (Protocol error), 0E (Protocol configuration failure), 0FH (Protocol negotiation failure), 10H (Session lost), 14H (Normal release)] 5-24

May 2007 7 (MSB) 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet 1 2 3 4 (LSB) System Time: A14 Element Identifier = [8CH] Length = [08H] CDMA System Time = <any value> n 1 2 3 4 (LSB) 10

Security Layer Packet: A14 Element Identifier = [89H] Length = [variable] Security Layer Packet

(MSB)

1 2 3

5.1.2.17

A14-Session Release Complete

The A14-Session Release Complete message is sent from the PCF to the AN to notify the AN that session release is complete. Information Element A14 Message Type ATI (UATI 32) Correlation ID Cause Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.9 Element Direction PCF AN PCF AN PCF AN PCF AN O Oa Ob Type M R C C

4 5 6 7

a. This information element shall only be included if it was also included in the A14-Session Release message. This information element shall be set to the value received in that message. b. This information element is used to indicate a failure situation if the session information is not reachable. When the AN receives this information element, it performs the session release procedure. The following table shows the bitmap layout for the A14-Session Release Complete message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI 32)] (LSB) 3 4 5 6 (LSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] 5-25 7 1 2 A14 Message Type = [2DH] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) UATIColorCode = <any value> UATI024 = <any value>

8

ATI (UATI 32): A14 Element Identifier = [80H]

A.S0007-A v3.0 HRPD IOS 7 (MSB) 6 5 4 3 2 1 0

May 2007 Octet 3 4 5 (LSB) Cause: A14 Element Identifier = [04H] Length = [01H] 05H (Session Unreachable)] 6 1 2 3

Correlation Value = <any value>

Cause Value = [

1 2 3

5.1.2.18

A14-Session Information Update

This message is sent from the AN to the PCF to update session information stored in the PCF during an active HRPD session. Information Element A14 Message Type ATI (UATI 32) Correlation ID Session State Information Record Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.7 Element Direction AN PCF AN PCF AN PCF AN PCF O Oa O

b

Type M R C R

4 5 6 7

a. If this information element is included in this message, its value shall be returned in the corresponding information element in the A14-Session Information Update Ack message sent in response to this message. b. Multiple copies of this information element may be included. The following table shows the bitmap layout for the A14-Session Information Update message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) (MSB) Session State Information Record: A14 Element Identifier = [8AH] Length = [variable] 5-26 6 1 2 (LSB) A14 Message Type = [32H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

8

May 2007 7 (MSB) 6 5 4 3 2 1 0 (LSB) Session State Information Record (LSB)

1 2 3

A.S0007-A v3.0 HRPD IOS Octet 3 4 n

5.1.2.19

A14-Session Information Update Ack

This message is sent from the PCF to the AN to acknowledge an A14-Session Information Update message. Information Element A14 Message Type ATI (UATI 32) Correlation ID Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 Element Direction PCF AN PCF AN PCF AN O O

a

Type M R C

4 5

a. This information element shall only be included if it was also included in the A14-Session Information Update message. This information element shall be set to the value received in that message. The following table shows the bitmap layout for the A14-Session Information Update Ack message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) 6 (LSB) A14 Message Type = [33H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

6

7 8

5.1.2.20

A14-Paging Request

This message is sent from the PCF to the AN to request that the AN start the paging procedure. Information Element A14 Message Type ATI (UATI 32) Correlation ID Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 Element Direction PCF AN PCF AN PCF AN O Oa Type M R C

5-27

A.S0007-A v3.0 HRPD IOS Information Element Sector ID (Registered Sector) Sector ID List Session State Information Record A14 Indicators

1 2 3 4 5

May 2007 Section Reference 5.2.2.5 5.2.2.6 5.2.2.7 5.2.2.8 Element Direction PCF AN PCF AN PCF AN PCF AN O Type O

b c

R C R R

O

O

a. If this information element is included in this message, its value shall be returned in the corresponding information element in the A14-Paging Request Ack message sent in response to this message. b. This information element is included if the PCF indicates a precise paging area. If this information element is included, the AT shall be paged on at least all sectors indicated in this list. c. Multiple copies of this information element may be included. The following table shows the bitmap layout for the A14-Paging Request message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI 32)] (LSB) 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) (MSB) (MSB) Sector ID (Registered sector): A14 Element Identifier = [88H] Length = [11H] SectorID Discriminator = [01H (SectorID128)] Sector ID = <any value> (LSB) 6 1 2 3 4 5 (LSB) Sector ID List: A14 Element Identifier = [81H] Length = [variable] SectorID Discriminator = [01H (SectorID128), 02H (SectorID32)] 19 1 2 3 A14 Message Type = [2EH] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) UATIColorCode = <any value> UATI024 = <any value>

6

IF (SectorID Discriminator = 01 H), SectorID128 Entry { 1+: 5-28

May 2007 7 (MSB) 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet k k+1 (LSB) k+15 k k+1 k+2 (LSB) k+3 1 2 (LSB) 3 4 (LSB) A14 Indicators: A14 Element Identifier = [82H] Length = [01H] Keep Alive Indicator =[0] Data Ready Indicator =[0,1] Paging Type Indicator =[0,1] A15 AuthentPaging ication Inhibited Required =[0,1] =[0,1] n 1 2 3

SectorID128 = <any value>

} OR IF (SectorID Discriminator = 02 H), SectorID32 Entry { 1+: (MSB) (MSB) ColorCode = <any value> SectorID24 = <any value> (LSB)

} SectorID32 Entry (MSB) (MSB) Session State Information Record: A14 Element Identifier = [8AH] Length = [variable] Session State Information Record

Reserved = [000]

1 2 3

5.1.2.21

A14-Paging Request Ack

This message is sent from the AN to the PCF in response to the A14-Paging Request message. This message is only sent if the Paging Type Indicator is set to `0' in the A14 Paging Request message. Information Element A14 Message Type ATI (UATI 32) Correlation ID Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 Element Direction AN PCF AN PCF AN PCF O O

a

Type M R C

4 5

a. This information element shall only be included if it was also included in the A14-Paging Request message. This information element shall be set to the value received in that message. The following table shows the bitmap layout for the A14-Paging Request Ack message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI 32)] 5-29 3 A14 Message Type = [2FH] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)]

6

A.S0007-A v3.0 HRPD IOS 7 (MSB) (MSB) 6 5 4 3 2 1 0 (LSB)

May 2007 Octet 4 5 6 (LSB) 7 1 2 3 4 5 (LSB) 6

UATIColorCode = <any value> UATI024 = <any value>

(MSB)

Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value>

1 2 3 4

5.1.2.22

A14-Paging Response

This message is sent from the AN to the PCF to report on the status of the paging procedure and to request the session information. This message is only sent if the Paging Type Indicator is set to `1' in the A14 Paging Request message. Information Element A14 Message Type ATI (UATI 32) Sector ID (Connected sector) Cause Section Reference 5.2.2.2 5.2.2.3 5.2.2.5 5.2.2.9 Element Direction AN PCF AN PCF AN PCF AN PCF O O

a

Type M R C R

O

5 6 7

a. This information element is included only when the cause value included in this message is set to `Paging completed successfully'. This information element contains the Sector ID of the sector in which the AT responded. The following table shows the bitmap layout for the A14-Paging Response message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI 32)] (LSB) 3 4 5 6 (LSB) (MSB) (MSB) Sector ID (Connected sector): A14 Element Identifier = [88H] Length = [11H] SectorID Discriminator = [01H (SectorID128)] Sector ID = <any value> (LSB) 7 1 2 3 4 5 5-30 A14 Message Type = [30H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) UATIColorCode = <any value> UATI024 = <any value>

8

May 2007 7 6 5 4 3 2 1 0 (LSB) Cause: A14 Element Identifier = [04H] Length = [01H] Cause Value = [01H (Paging completed successfully), 02H (Paging failed)]

1 2

A.S0007-A v3.0 HRPD IOS Octet 19 1 2 3

5.1.2.23

A14-Paging Response Ack

This message is sent from the PCF to the AN in response to the A14-Paging Response message. Information Element A14 Message Type ATI (UATI 32) Correlation ID Session State Information Record Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.7 Element Direction PCF AN PCF AN PCF AN PCF AN O O O

a b

Type M R C R

3 4 5

a. This information element shall only be included if it was also included in the A14-Paging Response message. This information element shall be set to the value received in that message. b. Multiple copies of this information element may be included. The following table shows the bitmap layout for the A14-Paging Response Ack message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI 32)] (LSB) 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) (MSB) (MSB) Session State Information Record: A14 Element Identifier = [8AH] Length = [variable] (LSB) Session State Information Record 5-31 6 1 2 3 4 A14 Message Type = [31H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) UATIColorCode = <any value> UATI024 = <any value>

6

A.S0007-A v3.0 HRPD IOS 7 6 5 4 3 2 1 0 (LSB)

1 2

May 2007 Octet n

5.1.2.24

A14-Keep Alive Request

This message is sent from the PCF to the AN to request the AN perform the Keep Alive procedure. Information Element A14 Message Type ATI (UATI 32) Correlation ID Sector ID Session State Information Record Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 5.2.2.5 5.2.2.7 Element Direction PCF AN PCF AN PCF AN PCF AN PCF AN O O O

a b

Type M R C C C

Oc

3 4 5 6 7 8 9 10

a. If this information element is included in this message, its value shall be returned in the corresponding information element in the A14-Keep Alive Request Ack message sent in response to this message. b. This information element is included when the PCF requests the AN to page the AT in an area associated with the Sector ID. c. This information element is included when the AN does not have the session state information for the AT (e.g., when the AT does not have an active connection). Multiple copies of this information element may be included. The following table shows the bitmap layout for the A14-Keep Alive Request message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) (MSB) Sector ID: A14 Element Identifier = [88H] Length = [11H] SectorID Discriminator = [01H (SectorID128)] 5-32 (LSB) 6 1 2 3 (LSB) A14 Message Type = [37H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

11

May 2007 7 (MSB) 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet 4 5 (LSB) 19 1 2 (LSB) 3 4 (LSB) n

Sector ID = <any value>

(MSB) (MSB)

Session State Information Record: A14 Element Identifier = [8AH] Length = [variable] Session State Information Record

1 2

5.1.2.25

A14-Keep Alive Request Ack

This message is sent from the AN to the PCF to acknowledge the A14-Keep Alive Request message. Information Element A14 Message Type ATI (UATI 32) Correlation ID Section Reference 5.2.2.2 5.2.2.3 5.2.2.4 Element Direction AN PCF AN PCF AN PCF O O

a

Type M R C

3 4

a. This information element shall only be included if it was also included in the A14-Keep Alive Request message. This information element shall be set to the value received in that message. The following table shows the bitmap layout for the A14-Keep Alive Request Ack message. 7 6 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 (LSB) (MSB) Correlation ID: A14 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) 6 (LSB) A14 Message Type = [38H] ATI: A14 Element Identifier = [80H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] UATIColorCode = <any value> UATI024 = <any value>

5

5-33

A.S0007-A v3.0 HRPD IOS

May 2007

1

5.1.3 5.1.3.1

A15 Message Definitions A15-Paging Request

2 3

This message is sent from the source AN to the target AN to request paging. Information Element A15 Message Type ATI (UATI 32) Correlation ID Sector ID List Session State Information Record A15 Indicators Section Reference 5.2.3.2 5.2.3.3 5.2.3.4 5.2.3.6 5.2.3.7 5.2.3.8 Element Direction source AN target AN source AN target AN source AN target AN source AN target AN source AN target AN source AN target AN O O O O

a

Type M R C C R C

Ob

c d

4 5 6 7 8 9 10 11

a. If this information element is included in this message, its value shall be returned in the corresponding information element in the A15-Paging Response message sent in response to this message. b. This information element indicates the sectors at the target AN which are to be used for paging. If this information element is not included, the target AN shall assume that all sectors under its control are to be used for paging. c. Multiple copies of this information element may be included. d. If this information element is not included in this message, the AN shall assume that all indicators are set to `0'. The following table shows the bitmap layout for the A15-Paging Request message. 7 6 5 4 3 2 1 0 A15 Message Type = [01H] ATI: A15 Element Identifier = [01H] Length = [05H] History Ind = [0H (Current)] (MSB) (MSB) ATI Type = [2H (UATI 32)] (LSB) UATIColorCode = <any value> UATI024 = <any value> (LSB) (MSB) Correlation ID: A15 Element Identifier = [02H] Length = [04H] Correlation Value = <any value>

12

Octet 1 1 2 3 4 5 6 7 1 2 3 4 5

(LSB) Sector ID List: A15 Element Identifier = [04H] Length = [variable] SectorID Discriminator = [01H (SectorID128), 02H (SectorID32)] 5-34

6 1 2 3

May 2007 7 (MSB) 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet k k+1 (LSB) k+15 k k+1 k+2 (LSB) k+3 1 2 (LSB) 3 4 (LSB) A15 Indicators: A15 Element Identifier = [06H] Length = [01H] Reserved = [0000 0] Data Paging AuthentReady Type ication Indicator Indicator Required =[0,1] =[0, 1] =[0,1] n 1 2 3

IF (SectorID Discriminator = 01 H), SectorID128 Entry { 1+: SectorID128 = <any value>

} OR IF (SectorID Discriminator = 02 H), SectorID32 Entry { 1+: (MSB) (MSB) ColorCode = <any value> SectorID24 = <any value> (LSB)

} Sector ID32 Entry (MSB) (MSB) Session State Information Record: A15 Element Identifier = [05H] Length = [variable] Session State Information Record

1 2

5.1.3.2

A15-Paging Response

This message is sent from the target AN to the source AN to report on the status of the paging procedure. Information Element A15 Message Type ATI (UATI 32) Correlation ID Sector ID (Connected sector) Section Reference Element Direction 5.2.3.2 5.2.3.3 5.2.3.4 5.2.3.5 target AN source AN target AN source AN target AN source AN target AN source AN O O

a

Type M R C R

Ob

3 4 5 6 7

a. This information element shall be included if it was also included in the A15-Paging Request message and shall be set to the value received in that message. Otherwise, this information element is optionally included. If included, its value shall be returned in the corresponding information element in the A15-Paging Response message. b. This information element contains the Sector ID of the sector in which the AT responded. The following table shows the bitmap layout for the A15-Paging Response message.

8

5-35

A.S0007-A v3.0 HRPD IOS 7 6 5 4 3 2 1 0

May 2007 Octet 1 1 2 ATI Type = [2H (UATI 32)] (LSB) 3 4 5 6 (LSB) 7 1 2 3 4 5 (LSB) 6 1 2 (LSB) 3 4 5 (LSB) 19

A15 Message Type = [02H] ATI: A15 Element Identifier = [01H] Length = [05H]

History Ind = [0H (Current)] (MSB)

UATIColorCode = <any value> UATI024 = <any value>

(MSB)

Correlation ID: A15 Element Identifier = [02H] Length = [04H] Correlation Value = <any value>

(MSB) (MSB)

Sector ID (Connected sector): A15 Element Identifier = [03H] Length = [11H] SectorID Discriminator = [01H (SectorID128)] Sector ID = <any value>

1 2 3

5.1.3.3

A15-Paging Response Ack

This message is sent from the source AN to the target AN to acknowledge the A15-Paging Response message. Information Element A14 Message Type ATI (UATI 32) Correlation ID Section Reference 5.2.3.2 5.2.3.3 5.2.3.4 Element Direction source AN target AN source AN target AN source AN target AN O Oa Type M R C

4 5

a. This information element shall only be included if it was also included in the A15-Paging Response message. This information element shall be set to the value received in that message. The following table shows the bitmap layout for the A15-Paging Response Ack message. 7 6 5 4 3 2 1 0 Octet 1 1 2 ATI Type = [2H (UATI 32)] 5-36 3 A15 Message Type = [03H] ATI: A15 Element Identifier = [01H] Length = [05H] History Ind = [0H (Current)]

6

May 2007 7 (MSB) (MSB) 6 5 4 3 2 1 0 (LSB)

A.S0007-A v3.0 HRPD IOS Octet 4 5 6 (LSB) Correlation ID: A15 Element Identifier = [02H] Length = [04H] Correlation Value = <any value> 7 1 2 3 4 5 (LSB) 6

UATIColorCode = <any value> UATI024 = <any value>

(MSB)

1 2

5-37

A.S0007-A v3.0 HRPD IOS

May 2007

1

5.2

5.2.1 5.2.1.1

Information Element Definitions

A13 Information Element Definitions Information Element Identifiers

2

3 4 5 6

The following table lists all the information elements that make up the messages defined in section 5.1.1. The table includes the Information Element Identifier (IEI) coding which distinguishes one element from another. The table also includes a section reference indicating where the element coding can be found. Element Name UATI 128 Security Layer Packet Sector ID Cause Mobile Identity (MN ID) PDSN IP Address Access Network Identifiers Session State Information Record IEI (Hex) 01H 02H 03H 04H 05H 06H 07H 08H IEI (Binary) 0000 0001 0000 0010 0000 0011 0000 0100 0000 0101 0000 0110 0000 0111 0000 1000 Reference 5.2.1.3 5.2.1.4 5.2.1.5 5.2.1.6 5.2.1.7 5.2.1.8 5.2.1.9 5.2.1.10

7 8

5.2.1.2

A13 Message Type

The A13 Message Type information element is used to indicate the type of message on the A13 interface. A13 Message Name A13-Session Information Request A13-Session Information Confirm A13-Session Information Reject A13-Session Information Response A13 Message Type 01H 02H 03H 04H Section Reference 5.1.1.1 5.1.1.3 5.1.1.4 5.1.1.2

9 10

5.2.1.3

Unicast Access Terminal Identifier (UATI 128).

This information element is set to the terminal identifier associated with the AT. 7 6 5 4 Length (MSB) UATI 3 2 1 0 Octet 1 2 3 4 (LSB) 18

A13 Element Identifier = [01H]

11 12 13 14

Length UATI

This field contains the number of octets in this information element following this field as a binary number. This field is set to the terminal identifier associated with the AT and is determined by the target AN. Refer to section 2.4.

5-38

May 2007

1 2

A.S0007-A v3.0 HRPD IOS Security Layer Packet

5.2.1.4

This information element is set to the security layer packet received from the AT. 7 6 5 4 Length (MSB) Security Layer Packet 3 2 1 0 Octet 1 2 3 4 (LSB) n

A13 Element Identifier = [02H]

3 4 5

Length

This field contains the number of octets in this information element following this field as a binary number.

Security Layer Packet This field is set to the security layer packet received from the AT. Refer to [10]. 5.2.1.5 Sector ID

6 7

This information element is set to the sector identifier associated with the AT. 7 6 5 4 Length (MSB) Sector ID 3 2 1 0 Octet 1 2 3 4 (LSB) 18

A13 Element Identifier = [03H]

8 9 10

Length Sector ID 5.2.1.6

This field contains the number of octets in this information element following this field as a binary number. This field is set to a 128-bit sector address. Refer to [10]. Cause

11 12 13

This information element is used to indicate the reason for occurrence of a particular event and is coded as follows. 7 6 5 4 Length (MSB) Cause Value (LSB) 3 2 1 0 Octet 1 2 3

A13 Element Identifier = [04H]

14 15 16

Length Cause Value

This field contains the number of octets in this information element following this field as a binary number. This field is set to the range of values as follows:

5-39

A.S0007-A v3.0 HRPD IOS Hex Values 01 02 03 04 05

1 2

May 2007 Cause Value Meaning Protocol subtype not recognized Protocol subtype attribute(s) not recognized Protocol subtype attribute(s) missing Requested session not found Requested session not authentic

5.2.1.7

Mobile Identity (MN ID)

This information element is used to provide the AT's Mobile Node Identification (MN ID). 7 6 5 4 Length

Identity Digit 1 Odd/even Indicator Type of Identity

3

2

1

0

Octet 1 2

3

A13 Element Identifier = [05H]

Identity Digit 3 Identity Digit N+1

Identity Digit 2 Identity Digit N Identity Digit N+2

4 n n+1

3 4

Length

This field contains the number of octets in this information element following this field as a binary number.

5

Type of Identity This field is defined as follows: Binary Values 000 110 Mobile Identity Meaning No Identity Code IMSI All other values are reserved.

6 7

Odd/Even Indicator (octet 3; bit 3) Identity Digits (octet 3 etc.)

This field is set to `0' for an even number of digits and to `1' for an odd number of identity digits. The IMSI Identity Digit fields are coded using BCD coding format. If the number of identity digits is even then bits 4 to 7 of the last octet shall be filled with an end mark coded as `1111'.

8 9 10

11 12

5.2.1.8

PDSN IP Address

This information element is used to provide the PDSN address. 7 6 5 4 Length (MSB) PDSN IP Address 3 2 1 0 Octet 1 2 3 4

A13 Element Identifier = [06H]

5-40

May 2007 7 6 5 4 3 2 1 0 (LSB)

1 2 3

A.S0007-A v3.0 HRPD IOS Octet 5 6

Length PDSN IP Address 5.2.1.9

This field contains the number of octets in this information element following this field as a binary number. This field is set to the IPv4 address of the source PDSN.

4 5 6 7

Access Network Identifiers

This information element uniquely identifies the PCF and is used by the PDSN to determine if it owns the connection. If so the PDSN does not need to send agent advertisements. If not, then the PDSN needs to trigger an MIP Registration Request so that the Foreign Agent/Home Agent tunnel is set up properly. 7 6 5 4 3 2 1 0 Octet 1 2 3 4 (LSB) (MSB) (MSB) NID (LSB) PZID This field identifies the ANID Sub Type (01H). This field contains the number of octets in this information element following this field as a binary number. This two octet field is coded to a value that uniquely identifies the cellular or PCS system. This two octet field is coded to a value that uniquely identifies the network within a cellular or PCS system. This one octet field is coded to a value that uniquely identifies the PCF coverage Area within a particular SID/NID area. The combined SID/NID/PZID triplet is unique to a PCF. Session State Information Record (LSB) 5 6 7 8

A13 Element Identifier = [07H] Type = 01H Length

Reserved

(MSB)

SID

8 9 10 11 12 13 14 15 16 17

Type Length SID NID PZID

18 19

5.2.1.10

This information element is used to send HRPD Session Information as specified in [10]. 7 (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 2 (LSB) Session State Information Record 3 4

A13 Element Identifier = [08H] Length = [variable]

5-41

A.S0007-A v3.0 HRPD IOS 7 6 5 4 3 2 1 0 (LSB)

1 2 3 4 5

May 2007 Octet n

Length Session State Information Record

This field contains the number of octets in this information element following this field as a binary number. This field contains the air interface protocol attributes and associated public data. The format is as specified in [10].

5-42

May 2007

A.S0007-A v3.0 HRPD IOS

1

5.2.2 5.2.2.1

A14 Information Element Definitions Information Element Identifiers

2 3 4 5

The following table lists all the information elements that make up the messages defined in section 5.1.2. The table includes the Information Element Identifier (IEI) coding which distinguishes one element from another. The table also includes a section reference indicating where the element coding can be found. Element Name Cause Correlation ID Access Network Identifiers ATI Sector ID List A14 Indicators Message Sequence Upper Old UATI Length Upper Old UATI UATI Subnet Mask Ax Traffic ID Sector ID Security Layer Packet Session State Information Record HRPD A9 Indicators System Time UATI Color Code IEI (Hex) 04H 13H 20H 80H 81H 82H 83H 84H 85H 86H 87H 88H 89H 8AH 8BH 8CH 8DH IEI (Binary) 0000 0100 0001 0011 0010 0000 1000 0000 1000 0001 1000 0010 1000 0011 1000 0100 1000 0101 1000 0110 1000 0111 1000 1000 1000 1001 1000 1010 1000 1011 1000 1100 1000 1101 Reference 5.2.2.9 5.2.2.4 5.2.2.16 5.2.2.3 5.2.2.6 5.2.2.8 5.2.2.11 5.2.2.12 5.2.2.13 5.2.2.14 5.2.2.15 5.2.2.5 5.2.2.10 5.2.2.7 Refer to [11]delta text in Annex A 5.2.2.17 5.2.2.18

6 7

5.2.2.2

A14 Message Type

The A14 Message Type information element is used to indicate the type of message on the A14 interface. A14 Message Name A14-General Update A14-General Update Complete A14-Authentication Command A14-Authentication Request A14-Authentication Response A14-Authentication Completed A14-Authentication Completed Ack A14-UATI Request A14-UATI Assignment A14-UATI Complete A14-UATI Complete Ack A14-UATI Assignment Failure 5-43 A14 Message Type 20H 21H 22H 23H 24H 25H 26H 27H 28H 29H 2AH 2BH Section Reference 5.1.2.6 5.1.2.7 5.1.2.8 5.1.2.9 5.1.2.10 5.1.2.11 5.1.2.12 5.1.2.1 5.1.2.2 5.1.2.3 5.1.2.4 5.1.2.5

A.S0007-A v3.0 HRPD IOS A14 Message Name A14-Session Release A14-Session Release Complete A14-Paging Request A14-Paging Request Ack A14-Paging Response A14-Paging Response Ack A14-Session Information Update A14-Session Information Update Ack A14-Session Release Command A14-Authentication Failure A14-Authentication Failure Ack A14-Keep Alive Request A14-Keep Alive Request Ack

1 2

May 2007 A14 Message Type 2CH 2DH 2EH 2FH 30H 31H 32H 33H 34H 35H 36H 37H 38H Section Reference 5.1.2.16 5.1.2.17 5.1.2.20 5.1.2.21 5.1.2.22 5.1.2.23 5.1.2.18 5.1.2.19 5.1.2.15 5.1.2.13 5.1.2.14 5.1.2.24 5.1.2.25

5.2.2.3

ATI (Access Terminal Identifier)

This information element is set to the terminal identifier associated with the AT. 7 6 5 4 Length History Ind (MSB) AT identifier ATI Type (LSB) 3 2 1 0 Octet 1 2 3 variable

A14 Element Identifier = [80H]

3 4

Length History Ind.

This field contains the number of octets in this information element following this field as a binary number. This field indicates ATI history. Valid values are as follows. ATI History Meaning Current used ATI Newly assignment ATI (reserved) Access Terminal identifier types associated with the AT are as follows. ATI Type Meaning Reserved (for Broadcast ATI (BATI)) Reserved (for Multicast ATI (MATI)) Unicast ATI 32 (UATI 32) Random ATI (RATI) Unicast ATI 128 (UATI128) (reserved) AT identifier Length (bits) N/A N/A 32 32 128

5

Binary Values 0000 0001 (all others)

6

ATI Type

Binary Values 0000 0001 0010 0011 0100 (all others)

7

5-44

May 2007

1

A.S0007-A v3.0 HRPD IOS

For UATI32 (Type 0010), the AT identifier field is encoded as follows. 7 (MSB) (MSB) 6 5 4 3 2 1 0 (LSB) Octet 3 4 5 6 (LSB) 7 History Ind UATIColorCode UATI024 ATI Type = [2H (UATI 32)]

2 3 4 5

ATI Type History Ind UATIColorCode UATI024

This field shall be set to `0010' (UATI 32). This field indicates ATI history. Refer to the ATI History Meaning, in this section. This field contains the UATIColorCode for the AT. Refer to [10]. This field contains the UATI024 for the AT. Refer to [10].

6

For RATI (Type 0011), the AT identifier field is encoded as follows. 7 (MSB) 6 5 4 RATI 3 2 1 0 Octet 3 4 5 6 (LSB) 7 History Ind ATI Type = [3H (RATI)]

7 8 9

ATI Type History Ind RATI

This field shall be set to `0011' (RATI). This field indicates ATI history. Refer to the ATI History Meaning, in this section. This field contains the RATI for the AT. Refer to [10].

10

For UATI128 (Type 0100), AT identifier field is encoded as follows. 7 (MSB) 6 5 4 3 UATI104 2 1 0 Octet 3 4 5 (LSB) (MSB) UATI024 (LSB) 16 17 18 19 History Ind ATI Type = [4H (UATI128)]

11 12 13 14 15

ATI Type History Ind UATI104 UATI024

This field shall be set to `0100' (UATI128). This field indicates ATI history. Refer to the ATI History Meaning, in this section. This field contains the UATI104 for the AT. Refer to [10]. This field contains the UATI024 for the AT. Refer to [10].

5-45

A.S0007-A v3.0 HRPD IOS

1 2

May 2007

5.2.2.4

Correlation ID

This information element is set to the correlation identifier associated with the AT. 7 6 5 4 3 2 1 0 Octet 1 2 3 4 5 (LSB) 6

A14 Element Identifier = [13H] Length = [04H] (MSB) Correlation Value

3 4 5 6

Length

This field contains the number of octets in this information element following this field as a binary number.

Correlation Value This field contains a value that allows an entity to correlate a request-response pair of messages. The value is a manufacturer concern. 5.2.2.5 Sector ID

7 8

This information element is set to the sector identifier associated with the AT. 7 6 5 4 Length (MSB) SectorID Discriminator Sector ID (LSB) 3 2 1 0 Octet 1 2 3 variable

A14 Element Identifier = [88H]

9 10

Length SectorID Discriminator Binary Values 0000 0001 0000 0010 (all others)

This field contains the number of octets in this information element following this field as a binary number. This field indicates SectorID Discriminator. Valid values are shown as follows. SectorID Discriminator Meaning SectorID 128 SectorID 32 (reserved)

11

12

For SectorID 128 (Type 0000 0001), the Sector ID field is encoded as follows. 7 (MSB) 6 5 4 3 Sector ID 2 1 0 Octet 4 18 (LSB) 19

13

For SectorID 32 (Type 0000 0010), the Sector ID field is encoded as follows.

5-46

May 2007 7 (MSB) (MSB) 6 5 4 3 2 1 0 (LSB)

A.S0007-A v3.0 HRPD IOS Octet 4 5 6 (LSB) 7

Color Code SectorID24

1 2 3

Sector ID Color Code SectorID24 5.2.2.6

This field contains the Sector ID for the AT. Refer to [10]. This field contains the Color Code for the AT. Refer to [10]. This field contains the SectorID24 for the AT. Refer to [10]. Sector ID List

4 5

This information element is set to the sector identifier associated with the AT. 7 6 5 4 Length SectorID Discriminator SectorID 1 SectorID n 3 2 1 0 Octet 1 2 3 4 n

A14 Element Identifier = [81H]

6 7 8 9

Length SectorID Discriminator SectorID 5.2.2.7

This field contains the number of octets in this element following this field as a binary number. For the definition of this field, refer to section 5.2.2.5, Sector ID. For the definition of this field, refer to section 5.2.2.5, Sector ID. Session State Information Record

10 11

This information element is set to the session state information record associated with the AT. 7 (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 2 (LSB) Session State Information Record (LSB) 3 4 n

A14 Element Identifier = [8AH] Length = [variable]

12 13 14 15

Length Session State Information Record

This field contains the number of octets in this information element following this field as a binary number. This field contains the air interface protocol attributes and associated public data. The format is as specified in [10].

16 17 18

5.2.2.8

A14 Indicators

This information element contains a number of indicators used to determine which procedures are to be followed by the receiver (e.g., whether inter-AN paging is prohibited or not). 5-47

A.S0007-A v3.0 HRPD IOS 7 6 5 4 3 2 1 0

May 2007 Octet 1 2 Paging A15 AuthentType Paging ication Indicator Inhibited Required 3

A14 Element Identifier = [82H] Length = [01H] Keep Data Alive Ready Indicator Indicator

Reserved

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

Length Authentication Required A15 Paging Inhibited Paging Type Indicator

This field contains the number of octets in this information element following this field as a binary number. If this field is set to `1', the AN should authenticate the AT. If this field is set to `1', the AN should not send an A15-Paging Request message to the neighbor ANs. If this field is set to `1', the AN should send an A14-Paging Response message to the PCF when the AT is successfully paged. If this field is set to `0', the AN should not send an A14-Paging Response message to the PCF. Instead, the AN should send an A14 Paging Request Ack message to the PCF. When the PCF has data to send when paging, this field is set to `1'. Therefore, the AN should try to establish an A8 connection. Otherwise, this field is set to `0'. This field is used to indicate to the PCF that the AT has initiated the Keep Alive procedure with the AN. The field is set `1' to indicate that the procedure has been performed, and is set to `0' otherwise.

Data Ready Indicator

Keep Alive Indicator

18 19 20

5.2.2.9

Cause

This information element is used to indicate the reason for occurrence of a particular event and is coded as follows. 7 6 5 4 Length (MSB) Cause Value (LSB) 3 2 1 0 Octet 1 2 3

A14 Element Identifier = [04H]

21 22 23

Length Cause Value

This field contains the number of octets in this information element following this field as a binary number. This field is set to the range of values as follows: Hex Values 01 02 03 04 05 06 A14 Cause Value Meaning Paging completed successfully Paging failed Authentication succeeded Authentication failure Session unreachable All session resources busy 5-48

May 2007 Hex Values 07 08 09 0A 0B 0C 0D 0E 0F 10 14 (all others)

1 2

A.S0007-A v3.0 HRPD IOS A14 Cause Value Meaning PCF resource unavailable AN-AAA unreachable Invalid session information AN resource unavailable Equipment failure Air link lost Protocol error Protocol configuration failure Protocol negotiation failure Session lost Normal release Reserved

5.2.2.10

Security Layer Packet

This information element is set to the security layer packet received from the AT. 7 6 5 4 Length (MSB) Security Layer Packet 3 2 1 0 Octet 1 2 3 4 (LSB) n

A14 Element Identifier = [89H]

3 4 5

Length

This field contains the number of octets in this information element following this field as a binary number.

Security Layer Packet This field is set to the security layer packet received from the AT. Refer to [10]. 5.2.2.11 Message Sequence

6 7

This information element is set to the message identifier associated with the AT. 7 6 5 4 3 2 1 0 Octet 1 2 (LSB) 3

A14 Element Identifier = [83H] Length = [01H] (MSB)

8 9 10 11

Message Sequence

Length Message Sequence

This field contains the number of octets in this information element following this field as a binary number. This field is set to the message sequence number that is used for the UATI Assignment procedure. Refer to [10].

5-49

A.S0007-A v3.0 HRPD IOS

1 2 3

May 2007

5.2.2.12

Upper Old UATI Length

This information element is used to indicate the number of least significant bytes of the AT parameter OldUATI[127:24]. 7 6 5 4 Length Reserved Upper Old UATI Length 3 2 1 0 Octet 1 2 3

A14 Element Identifier = [84H]

4 5 6 7

Length Upper Old UATI Length

This field contains the number of octets in this information element following this field as a binary number. This field is set to the number of least significant bytes of the AT parameter OldUATI[127:24].

8 9 10

5.2.2.13

Upper Old UATI

This information element is used to indicate the Upper Old UATI Length least significant bytes of the AT parameter OldUATI[127:24]. 7 6 5 4 Length (MSB) Upper Old UATI (LSB) 3 2 1 0 Octet 1 2 3 n

A14 Element Identifier = [85H]

11 12 13 14

Length Upper Old UATI

This field contains the number of octets in this information element following this field as a binary number. This field is set to the Upper Old UATI Length least significant bytes of the AT parameter OldUATI[127:24].

15 16

5.2.2.14

UATI Subnet Mask

This information element indicates the UATI Subnet Mask which the AT has been assigned. 7 6 5 4 3 2 1 0 Octet 1 2 (LSB) 3

A14 Element Identifier = [86H] Length = [01H] (MSB)

17 18 19

UATI Subnet Mask

Length UATI Subnet Mask 5.2.2.15 Ax Traffic ID

This field contains the number of octets in this information element following this field as a binary number. This field is set to an UATI Subnet Mask. Refer to [10].

20 21

This element is used to define an end-point for the Ax interface. 7 6 5 4 3 2 1 0 Octet 1

A14 Element Identifier = [87H] 5-50

May 2007 7 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet 2 3 4 (LSB) 5 6 7 8 (LSB) Address Type = [01H] (IPv4) 9 10 11

Length = [0CH] Ax transport protocol stack (MSB) (MSB) Protocol Type Key

MSB

IP Address

LSB

1 2

k

Length Ax transport protocol stack Hex Values 01H (all others)

This field contains the number of octets in this information element following this field as a binary number. This field indicates Ax transport protocol stack. Coded as follows: Ax Transport Protocol Stack Meaning GRE/IP (reserved) This field indicates Protocol Type. Coded as follows: Hex Values 88 0BH 88 81H (all others) Protocol Type Meaning PPP Unstructured byte stream (reserved)

3

4

Protocol Type

5 6 7

Key

This field indicates to the receiver the value to use in the GRE header Key field when sending GRE frames on the Ax bearer connection. This value is only unique within a single AN. This field indicates a type of AN address. Coded as follows: Hex Values 01H 02H (all others) Address Type Meaning IPv4 IPv6 (reserved) Length 4 16

8

Address Type

9 10

IP Address:

This field designates an end-point for the Ax interface. The internal format of this field is specified via the Address Type field.

5-51

A.S0007-A v3.0 HRPD IOS

1 2 3 4

May 2007

5.2.2.16

Access Network Identifiers

This information element uniquely identifies the PCF and is used by the PDSN to determine if it owns the connection. If so the PDSN does not need to send agent advertisements. If not, then the PDSN needs to trigger an MIP Registration Request so that the Foreign Agent/Home Agent tunnel is set up properly. 7 6 5 4 Length

Reserved

3

2

1

0

Octet 1 2 3

A14 Element Identifier = [20H] (MSB) SID (LSB) (MSB) (MSB)

5 6 7 8 9 10 11 12 13

4 5 6 7

NID (LSB) PZID (LSB)

Length SID NID PZID

This field contains the number of octets in this information element following this field as a binary number. This two octet field is coded to a value that uniquely identifies the cellular or PCS system. This two octet field is coded to a value that uniquely identifies the network within a cellular or PCS system. This one octet field is coded to a value that uniquely identifies the PCF coverage Area within a particular SID / NID area. The combined SID / NID / PZID triplet is unique to a PCF. System Time

14 15 16

5.2.2.17

This information element is used to validate the security layer packet included in the associated message. 7 6 5 4 3 2 1 0 Octet 1 2 3 4 (LSB) 10

A14 Element Identifier = [8CH] Length = [08H] (MSB) CDMA System Time

17 18 19 20 21

Length CDMA System Time

This field contains the number of octets in this information element following this field as a binary number. This is the common CDMA system-wide time to which all AN digital transmissions are referenced. Refer to [1].

22 23 24

5.2.2.18

UATI Color Code

This information element provides the color code when the ATI is a UATI128.

5-52

May 2007 7 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet 1 2 (LSB) 3

A14 Element Identifier = [8DH] Length = [01H] (MSB)

1 2 3 4 5

UATI Color Code

Length UATI Color Code

This field contains the number of octets in this information element following this field as a binary number. This field contains the UATI color code. Refer to [10].

5-53

A.S0007-A v3.0 HRPD IOS

May 2007

1

5.2.3 5.2.3.1

A15 Information Element Definitions Information Element Identifiers

2 3 4 5

The following table lists all the information elements that make up the messages defined in Section 5.1.3 The table includes the IEI coding which distinguishes one information element from another. The table also includes a section reference indicating where the information element coding can be found. Element Name ATI Correlation ID Sector ID Sector ID List Session State Information Record A15 Indicators IEI (Hex) 01H 02H 03H 04H 05H 06H IEI (Binary) 0000 0001 0000 0010 0000 0011 0000 0100 0000 0101 0000 0110 Reference 5.2.3.3 5.2.3.4 5.2.3.5 5.2.3.6 5.2.3.7 5.2.3.8

6 7

5.2.3.2

A15 Message Type

The A15 Message Type information element is used to indicate the type of message on the A15 interface. A14 Message Name A15 Message Type Section Reference A15-Paging Request A15-Paging Response A15-Paging Response Ack 01H 02H 03H 5.1.3.1 5.1.3.2 5.1.3.3

8 9

5.2.3.3

ATI (Access Terminal Identifier)

This information element is set to the terminal identifier associated with the AT. 7 6 5 4 Length History Ind (MSB) AT identifier (LSB) ATI Type 3 2 1 0 Octet 1 2 3 4 n

A15 Element Identifier = [01H]

10 11

Length History Ind. Binary Values 0000 0001 (all others)

This field contains the number of octets in this information element following this field as a binary number. This field indicates ATI history. Valid values are shown as follows. ATI History Meaning Current used ATI Newly assignment ATI (reserved) Access Terminal identifier types associated with the AT are as follows.

12

13

ATI Type

5-54

May 2007 Binary Values 0000 0001 0010 0011 0100 (all others)

1 2

A.S0007-A v3.0 HRPD IOS ATI Type Meaning Broadcast ATI (BATI) Multicast ATI (MATI) Unicast ATI 32 (UATI 32) Random ATI (RATI) Unicast ATI 128 (UATI128) (reserved) Octets 4-7 contain the ATI Identifier as described in [10]. For ATI Type `0010' (UATI32), the field is coded as follows. 6 5 4 UATI024 (LSB) 3 2 1 0 (LSB) Octet 4 5 6 7 AT identifier Length (bits) 0 32 32 32 128

ATI Identifier: 7 (MSB) (MSB)

UATIColorCode

3 4

5.2.3.4

Correlation ID

This information element is set to the correlation identifier associated with the AT. 7 6 5 4 3 2 1 0 Octet 1 2 3 4 5 (LSB) 6

A15 Element Identifier = [02H] Length = [04H] (MSB) Correlation Value = <any value>

5 6

Length

This field contains the number of octets in this information element following this field as a binary number.

7 8

Correlation Value This field contains a value that allows an entity to correlate a request-response pair of messages. The value is a manufacturer concern. 5.2.3.5 7 Sector ID 6 5 4 3 2 1 0 Octet 1 2 (LSB) 3 variable

9 10

This information element is set to the sector identifier associated with the AT. A15 Element Identifier = [03H] Length = [variable] (MSB) SectorID Discriminator Sector ID

11 12

Length

This field contains the number of octets in this information element following this field as a binary number. 5-55

A.S0007-A v3.0 HRPD IOS

1

May 2007 This field indicates SectorID Discriminator. Valid values are shown as follows. Binary Values Sector ID Discriminator Meaning 0000 0001 0000 0010 (all others) SectorID 128 SectorID 32 (reserved)

SectorID Discriminator

2

For SectorID 128 (Type 0000 0001), the Sector ID field is encoded as follows. 7 (MSB) 6 5 4 3 Sector ID 2 1 0 Octet 4 18 (LSB) 19

3

For SectorID 32 (Type 0000 0010), the Sector ID field is encoded as follows. 7 (MSB) (MSB) 6 5 4 3 2 1 0 (LSB) Octet 4 5 6 (LSB) 7 Color Code SectorID24

4 5 6

Sector ID Color Code SectorID24 5.2.3.6

This field contains Sector ID for the AT. Refer to [10]. This field contains the Color Code for the AT. Refer to [10]. This field contains the SectorID24 for the AT. Refer to [10]. Sector ID List Octet 1 2 3 4 n

7 8

This information element is set to the sector identifier list associated with the AT. 7 6 5 4 3 2 1 0 A15 Element Identifier = [04H] Length = [variable] SectorID Discriminator SectorID 1 SectorID n

9 10 11 12

Length

This field contains the number of octets in this information element following this field as a binary number. For the definition of this field, refer to section 5.2.3.5, Sector ID. Session State Information Record

SectorID Discriminator For the definition of this field, refer to section 5.2.3.5, Sector ID. Sector ID 5.2.3.7

13 14

This information element is set to the session state information record associated with the AT.

5-56

May 2007 7 (MSB) (MSB) 6 5 4 3 2 1 0

A.S0007-A v3.0 HRPD IOS Octet 1 2 (LSB) Session State Information Record (LSB) 3 4 n

A15 Element Identifier = [05H] Length = [variable]

1 2 3 4

Length Session State Information Record

This field contains the number of octets in this information element following this field as a binary number. This field contains the air interface protocol attributes and associated public data. The format is as specified in [10].

5 6

5.2.3.8 7

A15 Indicators 6 5 4 3 2 1 0 Octet 1 2 Data Paging Authentic Ready Type ation Indicator Indicator Required 3

This information element provides a status from the source AN requests to the target AN. A15 Element Identifier = [06H] Length = [01H] Reserved

7 8 9 10 11 12 13 14 15 16 17 18 19 20

Length Authentication Required Paging Type Indicator

This field contains the number of octets in this information element following this field as a binary number. If this field is set to `1', the AN should authenticate the AT. If this field is set to `0', the AN should send an A14-Paging Request Ack message to the PCF. If this field is set to `1', the AN should send an A14-Paging Response message to the PCF when the AT is successfully paged. When the source AN receives the Data Ready Indicator set to `1' from the PCF, the source AN shall set this field to `1'. In this case, the target AN should try to establish an A8 connection when it receives the HRPD connection request from the AT. Otherwise, this field is set to `0'.

Data Ready Indicator

5-57

A.S0007-A v3.0 HRPD IOS

May 2007

1

5.3

Timer Definitions

2

This section describes the timers associated with the HRPD IOS specification. Timer Name TA13req TA13res Tgu14 Tauthreq14 Tauthcom14 Tauthcomp14 Tauthfail14 Trelcom14 Tsu14 T14-UATI-Req T14-UATI-Assign T14-UATI-Comp Tpage14 Tprsp14 Tpreq14 Tkareq14 Trel14 Tprsp15 Tpreq15 Default Value (seconds) 1 1 1 1 1 1 1 12 1 1 1 1 12 1.5 1.5 1.5 1 1.5 Refer to 5.3.1.19 Range of Values (seconds) 0.1 - 60.0 0.1 - 60.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 5.0 0.1 ­ 5.0 0.1 ­ 60.0 0.1 ­ 60.0 0.1 ­ 5.0 0.1 ­ 60.0 Granularity (seconds) 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 Section Classification Reference 5.3.1.1 A13 interface 5.3.1.2 A13 interface 5.3.1.3 A14 interface 5.3.1.4 A14 interface 5.3.1.5 A14 interface 5.3.1.5 A14 interface 5.3.1.7 A14 interface 5.3.1.8 A14 interface 5.3.1.9 A14 interface 5.3.1.10 A14 interface 5.3.1.11 A14 interface 5.3.1.12 A14 interface 5.3.1.13 A14 interface 5.3.1.14 A14 interface 5.3.1.15 A14 interface 5.3.1.16 A14 interface 5.3.1.17 A14 interface 5.3.1.18 A15 interface 5.3.1.19 A15 interface

3

4

5.3.1 5.3.1.1

Timer Descriptions Timer TA13req

5 6 7 8

This PCF timer is started when the target PCF sends an A13-Session Information Request message to the source PCF and is stopped when the A13-Session Information Response message or A13-Session Information Reject message is received. 5.3.1.2 Timer TA13res

9 10 11

This PCF timer is started when the source PCF sends an A13-Session Information Response message to the target PCF and is stopped when the A13-Session Information Confirm message is received. 5.3.1.3 Timer Tgu14

12 13 14

This AN timer is started when the AN sends an A14-General Update message to the PCF and is stopped when the AN receives an A14-General Update Complete message from the PCF. 5.3.1.4 Timer Tauthreq14

15 16 17 18

This AN timer is started when the AN sends an A14-Authentication Request message to the PCF and is stopped when the AN receives an A14-Authentication Response message, an A14-Authentication Completed message or an A14-Authentication Failure Ack message from the PCF. 5-58

May 2007

1 2 3 4

A.S0007-A v3.0 HRPD IOS Timer Tauthcom14

5.3.1.5

This PCF timer is started when the PCF sends an A14-Authentication Command message to the AN, and stopped when the PCF receives either an A14-Authentication Request or an A14-Authentication Failure message from the AN. 5.3.1.6 Timer Tauthcomp14

5 6 7

This PCF timer is started when the PCF sends an A14-Authentication Completed message to the AN, and stopped when the PCF receives an A14-Authentication Completed Ack message from the AN. 5.3.1.7 Timer Tauthfail14

8 9 10

This AN timer is started when the AN sends an A14-Authentication Failure message to the PCF and is stopped when the AN receives an A14-Authentication Failure Ack message from the PCF. 5.3.1.8 Timer Trelcom14

11 12 13

This PCF timer is started when the PCF sends an A14-Session Release Command message to the AN and is stopped when the PCF receives an A14-Session Release message from the AN. 5.3.1.9 Timer Tsu14

14 15 16

This AN timer is started when the AN sends an A14-Session Information Update message to the PCF and is stopped when an A14-Session Information Update Ack message. 5.3.1.10 Timer T14-UATI-Req

17 18 19 20

This AN timer is started when the AN sends an A14-UATI Request message to the PCF and is stopped when the AN receives either an A14-UATI Assignment or A14-UATI Assignment Failure message from the PCF. 5.3.1.11 Timer T14-UATI-Assign

21 22 23 24 25

This PCF timer is started when the PCF sends an A14-UATI Assignment message to the AN, and stopped when the PCF receives an A14-UATI Complete message from the AN. The value of this timer should be greater than T14-UATI-Comp to allow for re-transmission of the A14UATI Complete message. 5.3.1.12 Timer T14-UATI-Comp

26 27 28

This AN timer is started when the AN sends an A14-UATI Complete message to the PCF and is stopped when the AN receives an A14-UATI Complete Ack message from the PCF. 5.3.1.13 Timer Tpage14

29 30 31 32

This PCF timer is started when the PCF sends an A14-Paging Request message to the AN with Paging Type Indicator set to `1' and stopped when the PCF receives an A14-Paging Response message from the AN. 5.3.1.14 Timer Tprsp14

33 34 35

This AN timer is started when the AN sends an A14-Paging Response message to the PCF and stopped when the AN receives an A14-Paging Response Ack message from the PCF.

5-59

A.S0007-A v3.0 HRPD IOS

1 2 3 4

May 2007

5.3.1.15

Timer Tpreq14

This PCF timer is started when the PCF sends an A14-Paging Request message to the AN with setting Page Type Indicator to `0', and stopped when the PCF receives an A14-Paging Request Ack message from the AN. 5.3.1.16 Timer Tkareq14

5 6 7

This PCF timer is started when the PCF sends an A14-Keep Alive Request message to the AN and is stopped when the PCF receives an A14-Keep Alive Request Ack message from the AN. 5.3.1.17 Timer Trel14

8 9 10

This AN timer is started when the AN sends an A14-Session Release message to the PCF, and is stopped when the AN receives an A14-Session Release Complete message from the PCF. 5.3.1.18 Timer Tprsp15

11 12 13

This AN timer is started when the target AN sends an A15-Paging Response message to the source AN, and stopped when the target AN receives an A15-Paging Response Ack message from the source AN. 5.3.1.19 Timer Tpreq15

14 15 16 17 18 19

This AN timer is started when the source AN sends an A15-Paging Request message to the target AN and stopped when the source AN receives an A15-Paging Response message or the source AN itself receives a paging response from the AT. The timer value is implementation specific.

5-60

May 2007

A.S0007-A v3.0 HRPD IOS

1

Annex A

2.14

A8-A9 (AN - PCF) Interface Change Text

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

Packet Data Calls

Data services are grouped into two categories: circuit-oriented (includes Asynchronous Data and Group-3 Fax services) and packet. Procedures applicable to packet data calls are described in this section. See section 6.2.2.66 for valid service options. Note some service options are only valid for Intergeneration Handoff (handoff between systems supporting packet data services based on ANSI/TIA/EIA/IS-95-B and systems supporting packet data service based on TIA/EIA/IS-2000). Intergeneration Handoffs are described in Annex D. Note: When the procedures between TIA/EIA/IS-95-B or 1x and HRPD systems differ, the HRPD procedures are identified separately within this specification. When the IOS text is applied to the HRPD RAN specification, the procedures related to the MSC shall be ignored. Hard Handoff procedures are not applicable to HRPD. For all calls supporting packet data services, a Packet Data Serving Node (PDSN) exists that interfaces between the transmission of the data in the fixed network and the transmission of the data over the air interface. The PDSN interfaces to the BS through a Packet Control Function (PCF), which may or may not be co-located with the BS. For purposes of the protocol of this standard, there are three packet data service states: Active/Connected, Dormant, and Null/Inactive. In the Active/Connected State, a physical traffic channel exists between the mobile station and the base station, and either side may send data. In the Dormant State, no physical traffic channel exists between the mobile station and the base station, but the PPP link between the mobile station and the PDSN is maintained. In the Null/Inactive State, there is no traffic channel between the mobile station and the base station and no PPP link between the mobile station and the PDSN.

Active / Connected State

Dormant State

Null / Inactive State

23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

Figure 2.14-1 - Packet Data Service State Transitions In 1x systems, A1 and A8 connections are maintained during the Active / Connected State and released during transition to Dormant or Null/Inactive State. The A10 connection is maintained during the Active/Connected and the Dormant State. In HRPD systems, the A8 connection is maintained during the Active/Connected State and released during transition to Dormant or Null/Inactive State. The A10 connection is maintained during the Active/ Connected and the Dormant State. As part of the support for the Dormant State, the TIA/EIA/IS-2000 air interface supports a Data Ready to Send indicator that is used on Origination. When a mobile terminal sends an origination request with a packet data service option specified, it will include the Data Ready to Send (DRS) bit. This indicator will be set to `1' on initial call setup and when the terminal wishes to transition from Dormant to Active because it has data to send and is requesting the establishment of a traffic channel. The DRS bit will be set to `0' to indicate that the terminal has transitioned a Packet Zone boundary while dormant, and is sending the origination request to update the network as to its current location. A-1

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

May 2007

In HRPD systems when data is ready to be sent, connection establishment procedures are used on initial call setup to transition from Dormant to Active for the purposes of requesting the establishment of a traffic channel. UATI assignment procedures are employed when the terminal detects a change of subnet while dormant, to update the network as to its current location. On receipt of an origination with the DRS bit set to `1' or for connection establishment procedures in an HRPD system, the BS will initiate the call setup procedure as shown in section 2.14.7.1, which will normally result in the establishment of a traffic channel and in the A8 and A10 bearer connections being established. In 1x systems, wWhen the BS receives an origination with the DRS bit set to `0' the BS will delay the establishment of a traffic channel until after the A8 and A10 bearer connection establishment procedures are complete. During the A8 bearer connection establishment procedure, the BS will indicate to the PCF that a DRS=0 has been received through the use of the Data Ready Indicator element in the A9-Setup-A8 message. If the PCF has data from the network to deliver to the terminal, it will indicate this by setting the Cause element in the A9-Connect-A8 message to the Data Ready to Send value. The BS will then establish a traffic channel to the terminal and complete a normal call setup procedure as in section 2.14.7.1. For HRPD systems, the AN initiates connection establishment procedures to setup a traffic channel with the AT. If the PCF does not have data, it indicates that the A8 is not being established by sending the A9-ReleaseA8 Complete message to the BS. The BS will then return an Assignment Failure message to the MSC with the cause value set to Packet call going dormant. Upon receipt of the Assignment Failure message, the MSC returns a Clear Command to the BS with the Cause value set to Do Not Notify Mobile. The BS sends a Clear Complete message to the MSC upon receipt of the Clear Command message. 2.14.1 Packet Data Assumptions No changes from TIA/EIA/IS-2001-A text. 2.14.2 Previous and Current Access Network Identifiers (PANID/CANID) The selected PDSN needs to know whether a mobile is being handed off by a PCF that was not previously using this PDSN for the connection, in order to determine if PPP reconfiguration and Mobile IP registration are required. The information used to make this determination consists of the PZID, SID or NID (PZID), System ID (SID) and Network ID (NID) values, which are also referred to as the Access Network Identifiers. The PCF is uniquely identified by the Current Access Network Identifiers (CANID) and every PCF knows its CANID value. Anytime a mobile crosses into a new region, where the region is defined by the Access Network Identifiers, it must re-register with that Access Network. On detection of a new PZID, SID or NID, the Mobile Station sends an Origination message or Enhanced Origination message to the target BS. In an HRPD system the change of PZID, SID and NID is indicated by the location update procedures as defined in TIA/EIA/IS-856. The target BS forwards the received PZID, SID and NID information to the PCF as the Previous Access Network Identifiers (PANID). The AN may also retrieve the PZID, SID and NID from the AT in an HRPD system by using the location update procedures in TIA/EIA/IS-856 when the AN detects a dormant handoff between subnets. In the case of hard handoff, the source BS includes the Previous Access Network Identifiers (PANID) in the Handoff Required message to the MSC. The MSC forwards this information to the target BS in the Handoff Request message, which in turn sends the received PANID to the PCF. The PCF includes the PANID received from the target BS, along with the its own Current Access Node Identifiers (CANID) to the PDSN as part of the A11-Registration Request message. The PDSN maintains the CANID which is serving each connection and compares this against the PANID, received in the A11 Registration Request, to determine if it currently owns the call. If the PDSN owns the call, it does not need to initiate or send agent advertisements. If the PDSN does not own the call, then the PDSN needs to trigger PPP renegotiation followed by the sending of agent advertisement messages so that a new Foreign Agent / Home Agent (HA) tunnel to the mobile can be setup properly. Upon a successful A11 registration, the PDSN

23 24

25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48

A-2

May 2007

1 2

A.S0007-A v3.0 HRPD IOS

updates its stored CANID with the input CANID value received in the A11-Registration Request message (so it is up-to-date with the currently active PCF). For first time originations the Mobile Station does not send the PANID and the PCF sends only its CANID. If the PDSN does not receive the PANID, it performs an agent advertisement and forces the mobile to re-register with the Home Agent. 2.14.3 PDSN Selection Algorithm

3 4 5

6 7

No changes from TIA/EIA/IS-2001-A text. 2.14.4 A8/A9 Interface Procedures No changes from TIA/EIA/IS-2001-A text. 2.14.4.1 A8/A9 Interface Setup Procedures and Messages

8 9

10 11

No changes from TIA/EIA/IS-2001-A text. 2.14.4.1.1 A9-Setup-A8

12 13

No changes from TIA/EIA/IS-2001-A text. 2.14.4.1.1.1 Successful Operation

14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

When the BSC receives an Assignment Request from the MSC, as a result of sending a CM Service Request (in response to an Origination message from the mobile with a Service Option that requests packet data service and with the DRS bit set to `1'), or as a result of sending a Page Response, or when connection establishment procedures are employed in an HRPD system, it initiates the procedure for establishing radio traffic channels. In the case where the AN does not have the session information required to establish the traffic channel, the traffic channel is established after the A8 establishment procedure and retrieval of session information from the PCF. After establishing traffic channels, the BSC determines the characteristics for an A8 connection such as QoS and generates an A9-Setup-A8 message indicating the normal call setup (i.e., the handoff indicator field of the A9-Setup-A8 message is set to `0'). In an HRPD system, the AN includes the Session Information Required Indicator in the A9-Setup-A8 message, if the AN does not have session information to establish a traffic channel. The BSC sends the message to the PCF on the A9 interface and starts timer TA8-setup. Upon receiving the message, the PCF initiates the procedure for establishing an A10 connection. After establishing an A10 connection, the PCF sends an A9-Connect-A8 message to the BSC. For the case where the DRS bit received from the mobile is set to `0' or a request for a traffic channel is not received in the HRPD system, the BSC will await the response from the PCF to determine if a traffic channel needs to be established. In an HRPD system, the PCF includes session information in the A9Connect-A8 message if the Session Information Required Indicator is included in the A9-Setup-A8 message. When the mobile station performs a hard handoff during packet services, the target BSC sends the A9Setup-A8 message upon receipt of the Handoff Request message from the MSC and starts timer TA8-setup. In this case, the BSC sets the Handoff Indicator field of the A9-Setup-A8 message to `1' and Data Ready Indicator is set to `1'. In the case of dormant handoff the BSC sends the A9-Setup-A8 message to the PCF upon receipt of the Assignment Request message from the MSC. For this case, it will set both the Data Ready Indicator and the Handoff Indicator to 0. Please refer to section 6.1.10.1, "A9-Setup-A8," for the format and content of this message. Alternatively, if upon receipt of the A9-Setup-A8 message, if the PDSN has no data to send to the MS (in the case of a dormant handoff) or if the PCF could not setup the A8 connection due to PDSN resources being unavailable, the PCF will send the A9-Release-A8 Complete message. Upon receipt of this message, the BSC stops timer TA8-setup. A-3

A.S0007-A v3.0 HRPD IOS

1 2

May 2007

If the A9-Setup-A8 message contains a DRI set to '0' and the PCF does not have data to send, the PCF rejects the attempt to setup the A8 connection by sending an A9-Release-A8 Complete message to the BSC. 2.14.4.1.1.2 Failure Operation

3 4 5 6 7 8 9 10 11 12

If the BSC fails to receive an A9-Connect-A8 message, that is to say, the timer TA8-setup has expired before receiving an A9-Connect-A8 or A9-Release-A8 Complete message, the BSC sends an Assignment Failure message or a Handoff Failure message, as appropriate, to the MSC. If the A10/A11 connection establishment procedure is required but fails, the PCF should send an A9-Release-A8 Complete message with cause value set to "PDSN resources not available (0x79)". In an HRPD system, if the AN fails to receive an A9-Connect-A8 message or an A9-Release-A8 Complete message, the AN may re-send the A9-Setup-A8 message or release the traffic channel if it exists. If the PCF decides that validation of the Security Layer Packet received in the A9-Setup-A8 message failed, the PCF shall send an A9-Release-A8 Complete message with cause value indicating `Authentication Failure'. 2.14.4.1.2 A9-Connect-A8

13 14

No changes from TIA/EIA/IS-2001-A text. 2.14.4.1.2.1 Successful Operation

15 16

No changes from TIA/EIA/IS-2001-A text. 2.14.4.1.2.2 Failure Operation

17 18

No changes from TIA/EIA/IS-2001-A text. 2.14.4.1.3 A9-BS Service Request

19 20

No changes from TIA/EIA/IS-2001-A text. 2.14.4.1.3.1 Successful Operation

21 22

No changes from TIA/EIA/IS-2001-A text. 2.14.4.1.3.2 Failure Operation

23 24

No changes from TIA/EIA/IS-2001-A text. 2.14.4.1.4 A9-BS Service Response

25 26

No changes from TIA/EIA/IS-2001-A text. 2.14.4.1.4.1 Successful Operation

27 28

No changes from TIA/EIA/IS-2001-A text. 2.14.4.1.4.2 Failure Operation

29 30

No changes from TIA/EIA/IS-2001-A text. 2.14.5 A8/A9 Interface Clearing Procedures and Messages

31 32

No changes from TIA/EIA/IS-2001-A text. 2.14.5.1 · Successful Clearing Scenarios

33 34 35 36

An A8 connection clearing occurs: when a packet data inactivity timer in the BSC expires. The BSC, after sending the Clear Request message, sets timer T300 and waits for a Clear Command message from the MSC. To release all A-4

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

A.S0007-A v3.0 HRPD IOS

allocated resources, the MSC shall send a Clear Command message to the BSC, start timer T315, and wait for the Clear Complete message from the BSC. After stopping timer T300 and releasing the air resources, the BSC sends an A9-Release-A8 message to the PCF and starts timer Trel9. The PCF responds with an A9-Release-A8 Complete message. Then the BSC sends a Clear Complete message and stops timer Trel9. The 1x system call flow scenario is illustrated in section 2.14.7.2, BS Initiated Call Release to Dormant State. The HRPD system call flow scenario is illustrated in TIA-878 section 3.4.2, Connection Release on HRPD Network - Initiated by the AN. · when the packet data inactivity timer in the MS expires. When the BS receives a Release Order or connection release procedures for HRPD systems, requesting the transition to dormant, the BSC shall send a Clear Request message to the MSC. The rest of the procedure is same as the BSC initiated scenario. The 1x system call flow scenario is illustrated in section 2.14.7.3, MS Initiated Call Release to Dormant State. The HRPD system call flow scenario is illustrated in TIA-878 section 3.4.1, Connection Release on HRPD Network - Initiated by the AT. when the MS releases the call or to indicate to the BSC that an A8 connection will not be established due to either PDSN resources being unavailable or during dormant handoff if the PDSN has no data to send. When the BSC receives a Release Order or connection release procedures for HRPD systems, the BSC shall send a Clear Request message to the MSC and start timer T300. To release all allocated resources, the MSC shall send a Clear Command message to the BSC, start timer T315, and wait for the Clear Complete message from the BSC. After stopping timer T300 and releasing the air resources with the Release Order or connection release procedures for HRPD systems, the BSC sends an A9Release-A8 message to the PCF and starts timer Trel9. The PCF responds with an A9-Release-A8 Complete message. Then the BSC sends a Clear Complete message and stops timer Trel9. The 1x system call flow scenario is illustrated in section 2.14.7.4, MS Power Down. The HRPD system call flow scenario is illustrated in TIA-878 section 3.4.1, Connection Release on HRPD Network Initiated by the AT. when the A10/A11 connection is released by the PDSN. When the PCF detects that the A10/A11 connection is released, the PCF sends an A9-Disconnect-A8 message to the BSC and starts timer Tdiscon9. Then the BSC initiates the release of the A8 connection by sending an A9-Release-A8 message and starts timer Trel9. The PCF responds with an A9-Release-A8 Complete message and stops timer Tdiscon9. The BSC, after sending the Clear Request message and stopping timer Trel9, sets timer T300 and waits for a Clear Command message from the MSC. To release all allocated resources, the MSC shall send a Clear Command message to the BSC, start timer T315, and wait for the Clear Complete message from the BSC. Then the BSC stops timer T300, releases the air resources, and responds with a Clear Complete message. The 1x system call flow scenario is illustrated in section 2.14.7.5, PDSN Initiated Service Release. The HRPD system call flow scenario is illustrated in TIA878 section 3.5.5, HRPD Session Release - Initiated by the PDSN. Unsuccessful A8 Interface Clearing Procedures

·

·

37 38

2.14.5.2

No changes from TIA/EIA/IS-2001-A text. 2.14.5.3 A9-Release-A8

39 40

No changes from TIA/EIA/IS-2001-A text. 2.14.5.3.1 Successful Operation

41 42

No changes from TIA/EIA/IS-2001-A text. 2.14.5.3.2 Failure Operation

43 44

No changes from TIA/EIA/IS-2001-A text.

A-5

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6

May 2007

2.14.5.4

A9-Release-A8 Complete

No changes from TIA/EIA/IS-2001-A text. This A9 interface message is sent from the PCF to the BSC to acknowledge completion of the request to release the A8 connection or to indicate to the BSC that an A8 connection has not been established due to either PDSN resources being unavailable, or during dormant handoff if the PDSN has no data to send or as a requirement of terminal authentication in HRPD systems. 2.14.5.4.1 Successful Operation

7 8

No changes from TIA/EIA/IS-2001-A text. 2.14.5.4.2 2.14.5.5 2.14.5.5.1 Failure Operation A9-Disconnect-A8 Successful Operation

9 10 11 12 13 14

No changes from TIA/EIA/IS-2001-A text. No changes from TIA/EIA/IS-2001-A text. No changes from TIA/EIA/IS-2001-A text. 2.14.5.5.2 2.14.5.6 Failure Operation A9-Update-A8

15 16 17 18

No changes from TIA/EIA/IS-2001-A text. No changes from TIA/EIA/IS-2001-A text. 2.14.5.6.1 Successful operation

19 20

No changes from TIA/EIA/IS-2001-A text. 2.14.5.6.2 Failure operation

21 22

No changes from TIA/EIA/IS-2001-A text. 2.14.5.7 A9-Update-A8 Ack

23 24

No changes from TIA/EIA/IS-2001-A text. 2.14.5.7.1 Successful operation

25 26

No changes from TIA/EIA/IS-2001-A text. 2.14.5.7.2 Failure operation

27 28

No changes from TIA/EIA/IS-2001-A text. 2.14.6 A8/A9 Interface Handoff Procedures and Messages

29 30

No changes from TIA/EIA/IS-2001-A text. 2.14.6.1 A9-Air Link (AL) Connected

31 32 33 34 35 36

In 1x systems,A after the mobile station performs (inter-BS) hard handoff, the A9-AL Connected message is sent from the target BS managing the active air link to the target PCF. This message is employed in order to notify the target PCF that handoff is successfully completed and that the air link has been established and that the PCF can send packets on the new A8 connection. An A9-AL Connected Ack message is expected in response in a successful situation. If the target PCF was not able to establish an A-6

May 2007

1 2 3 4 5 6

A.S0007-A v3.0 HRPD IOS

A10 connection with a selected PDSN, it will send back an A9-Disconnect-A8 message to the BSC to release the A8 connection. In HRPD systems, the A9-AL Connected message is sent from the AN managing the active air link to the PCF when it determines that data flow stopped by the A9-AL Disconnected message from the PCF should be resumed. This message is employed to notify the PCF that it can send packets on the A8 connection. An A9-AL Connected Ack message is expected in response to this message. 2.14.6.1.1 Successful Operation

7 8 9 10 11 12 13 14 15 16 17 18 19 20

In 1x systems, Aafter the mobile station performs (inter-BS) hard handoff including the case of return on failure, the (target) BSC managing the active air link sends the A9-AL Connected message to the (target) PCF and starts timer Talc9. Upon the receipt of the A9-AL Connected message, the PCF updates its routing table to route packet data sent from the PDSN to the (target) BSC managing the active air link. The PCF performs A10/A11 connection establishment if the A10/A11 connection has not been established yet. If the PCF is unable to establish the new A10/A11 connection, it will send an A9-Disconnect-A8 message to the BSC. Upon receipt of this message, the BSC will begin call tear-down. In HRPD systems, when the AN determines that data flow stopped by the A9-AL Disconnected message from the PCF should be resumed, it sends the A9-AL Connected message to the PCF and starts timer Talc9. Upon the receipt of the A9-AL Connected message, the PCF updates its routing table to route packet data sent from the PDSN to the AN managing the active air link. Please refer to section 6.1.10.8, "A9-AL Connected", for the format and content of this message. 2.14.6.1.2 Failure Operation

21 22

No changes from TIA/EIA/IS-2001-A text. 2.14.6.2 A9-Air Link (AL) Connected Ack

23 24

No changes from TIA/EIA/IS-2001-A text. 2.14.6.2.1 Successful Operation

25 26

No changes from TIA/EIA/IS-2001-A text. 2.14.6.2.2 Failure Operation

27 28

No changes from TIA/EIA/IS-2001-A text. 2.14.6.3 A9-Air Link (AL) Disconnected

29 30 31 32 33

When the mobile station performs hard handoff or the AN determines that data flow from the PCF should be stopped, the A9-AL Disconnected message is sent from the source BSC to the source PCF. This message is employed in order to notify the source PCF that the air link is temporarily disconnected. An A9-AL Disconnected Ack message is expected in response. 2.14.6.3.1 Successful Operation

34 35 36 37 38 39 40

When the source BSC receives the Handoff Command message which instructs it to perform hard handoff or when the AN determines that data flow from the PCF should be stopped in the HRPD system, the source BSC shall send an A9-AL Disconnected message to the PCF and start timer Tald9. Upon receipt of an A9-AL Disconnected message from the source BSC, the PCF shall stop transmitting packet data and start buffering packets from the PDSN. Please refer to section 6.1.10.10, "A9-AL Disconnected," for the format and content of this message.

A-7

A.S0007-A v3.0 HRPD IOS

1 2

May 2007

2.14.6.3.2

Failure Operation

No changes from TIA/EIA/IS-2001-A text. 2.14.6.4 A9-Air Link (AL) Disconnected Ack

3 4

No changes from TIA/EIA/IS-2001-A text. 2.14.6.4.1 Successful Operation

5 6

No changes from TIA/EIA/IS-2001-A text. 2.14.6.4.2 Failure Operation

7 8 9 10

No changes from TIA/EIA/IS-2001-A text. 6.1.10 6.1.10.1 A9 Interface Message Formats A9-Setup-A8

11 12 13

This A9 interface message is sent from the BS to the PCF to request the establishment of an A8 connection.

Information Element A9 Message Type Call Connection Reference Correlation ID Mobile Identity (IMSI/ATI) Mobile Identity (ESN) CON_REF Quality of Service Parameters A9 BSC_ID A8_Traffic_ID Service Option A9 Indicators User Zone ID IS-2000 Service configuration record Access Network Identifiers PDSN IP Address Sector ID Security Layer Packet System Time HRPD A9 Indicators Section Reference Element Direction 6.2.2.167 6.2.2.98 6.2.2.108 6.2.2.16 6.2.2.16 6.2.2.168 6.2.2.54 6.2.2.169 6.2.2.170 6.2.2.66 6.2.2.171 6.2.2.32 6.2.2.68 6.2.2.189 6.2.2.30 6.2.2.198 6.2.2.199 6.2.2.200 6.2.2.201 BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF O Oa Og Ob Oh Oc O O Of O Oi Oe Od Oj Ok Ol Om On Type M R C R C R C R R R R C C C C C C C C

14 15

a. If this element is included in this message, its value shall be returned in the corresponding element in the A9-Connect A8 message sent in response to this message.

A-8

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

A.S0007-A v3.0 HRPD IOS

b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS. Use of the ESN in this message is a network operator decision. This information element shall not be included in HRPD messages. c. This information element is included if information is available at the BS. In this version of this standard, this element is used to carry the current non-assured mode priority of the packet data session. This information element shall not be included in HRPD messages. d. The Access Node Identifiers (PANID) are included if received from the MS. e. This information element may be omitted if the BS does not possess this information at the time the message if created. This information element shall not be included in HRPD messages. f. The User Zone ID is included if received from the MS. g. The IMSI shall be included in 1x systems. In HRPD messages the revision 0 AN sets this information element to the MN ID associated with the A10 connection, otherwise, UATI32 is used. h. The IS-2000 CON_REF field of this information element shall be set to 00H for padding, in HRPD messages. i. j. This information element shall not be included in HRPD messages. If this information element is included in the A13-Session Information Response message, then this information element is included and contains the value received in the A13-Session Information Response message.

k. This information element shall not be included in 1x systems. In HRPD messages, the AN shall include this information element which indicates the sector where the AN receives message from the AT. l. This information element shall not be included in 1x systems. In HRPD messages, the AN shall include this information element if the security layer packet has to be validated and the AN cannot validate security layer packet received from the AT.

m. This information element is used to validate the security layer packet included in this message. n. This information element shall not be included in 1x systems. In HRPD messages, the PCF assumes that all indicators are set to `0' if this information element is not included in the message.

A-9

A.S0007-A v3.0 HRPD IOS

1

May 2007

The following table shows the bitmap layout for the A9-Setup-A8 message:

7 (MSB) (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> 4 5 6 7 8 9 (LSB) (MSB) Correlation ID: A3/A7 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 10 1 2 3 4 5 (LSB) Mobile Identity (IMSI/ATI)): A1 Element Identifier = [0DH] Length = [06H-08H] (10-15 digits) Identity Digit 1 = [0H-9H] (BCD) Odd/even Indicator = [1,0] Type of Identity = [110 (IMSI), 111 (ATI)] 6 1 2 3

A9 Message Type = [01H] A1 Element Identifier = [3FH]

Call Connection Reference:

Length = [08H] Market ID = <any value>

Identity Digit 3 = [0H-9H] (BCD) Identity Digit N+1 = [0H-9H] (BCD) = [1111] (if even number of digits) History Ind = [0H (Current)] (MSB) (MSB)

Identity Digit 2 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD) ATI Type = [2H (UATI 32)] (LSB)

4 n n+1 4 5 6 7

UATIColorCode = <any value> UATI024 = <any value>

(LSB) -- Continued on next page --

8

A-10

May 2007

1

A.S0007-A v3.0 HRPD IOS

-- Continued from previous page - Mobile Identity (ESN): A1 Element Identifier = [0DH] Length = [05H] Identity Digit 1 = [0000] Odd/even Indicator = [0] ESN = <any value> Type of Identity = [101] (ESN) 1 2 3

(MSB)

4 5 6 (LSB) 7 1 2 3 1 2 3 1 2 3 (LSB) m 1 2 3 4 (LSB) 5 6 7 8 (LSB) 9 10 11 12 13 (LSB) 14

CON_REF:

A9 Element Identifier = [01H]

Length = [01H] IS-2000 CON_REF = [00H ­ FFH] Quality of Service Parameters: Reserved = [0000] (MSB) A9 BSC_ID: A9 Element Identifier = [07H]

Length = [01H] Non-Assured Mode Packet Priority = [0000 ­ 1101] A9 Element Identifier = [06H]

Length = [01H ­ 06H] BSC Identifier = <any value>

A8 Traffic ID:

A9 Element Identifier = [08H]

Length = [0CH] A8 transport protocol stack = [01H] (GRE/IP) (MSB) (MSB) Protocol Type = [88 81H] (Unstructured byte stream) Key = <any value>

Address Type = [01H] (IPv4) (MSB) IP Address = <any value>

-- Continued on next page --

A-11

A.S0007-A v3.0 HRPD IOS

1

May 2007

-- Continued from previous page - (MSB) Service Option: A1 Element Identifier = [03H] Service Option

3

1 2 (LSB) 3 1 2 Handoff iIndicato r = [0, 1] 3

= [ 00 21H (3G High Speed Packet Data) 00 3BH (High Rate Packet Data) ] A9 Indicators: A9 Element Identifier = [05H] Data Ready Indicator = [0,1]

Length = [01H] Reserved = [0000 000]

(MSB)

User Zone ID:

A1 Element Identifier = [02H]

1 2 3 (LSB) 4 1 2 3 4

Length = [02H] UZID = <any value>

IS-2000 Service Configuration Record: Reserved = [ 0000 0 ]

A1 Element Identifier = [0EH] Bit-Exact Length ­ Fill Bits = [ 000 ­ 111 ]

Bit-Exact Length ­ Octet Count = <variable>

(MSB) IS-2000 Service Configuration Record Content = <any value> Seventh Fill Bit ­ if needed = [0 (if used as a fill bit)] Reserved (MSB) (MSB) Sixth Fill Bit ­ if needed = [0 (if used as a fill bit)] Fifth Fill Bit ­ if needed = [0 (if used as a fill bit)] Fourth Fill Bit ­ if needed = [0 (if used as a fill bit)] Third Fill Bit ­ if needed = [0 (if used as a fill bit)] Second Fill Bit ­ if needed = [0 (if used as a fill bit)] First Fill Bit ­ if needed = [0 (if used as a fill bit)]

... k

Access Network Identifiers: (MSB)

A1 Element Identifier = [20H]

1 2 3 (LSB) 4 5 (LSB) 6 7 (LSB)

Length = [05H] SID = <any value> NID = <any value> PZID = <any value> -- Continued on next page --

3

SO 59 (00 3BH) is used for HRPD.

A-12

May 2007

1

A.S0007-A v3.0 HRPD IOS

-- Continued from previous page - (MSB) PDSN IP Address: A1 Element Identifier = [14H] 1 2 3 4 5 (LSB) Sector ID: A14 Element Identifier = [88H] Length = [11H] SectorID Discriminator = [01H (SectorID128)] (MSB) Sector ID = <any value> 6 1 2 3 4 5 (LSB) (MSB) Security Layer Packet: A14 Element Identifier = [89H] Length = [variable] Security Layer Packet 19 1 2 3 4 (LSB) (MSB) System Time: A14 Element Identifier = [8CH] Length = [08H] CDMA System Time = <any value> n 1 2 3 4 (LSB) HRPD A9 Indicators: Reserved = [0000 00] A9 Element Identifier = [8BH] Default Session Indicator = [0] Session Informat ion Required = [0, 1] 10 1 2 3

Length = [04H] PDSN IP Address = <any value>

Length = [01H]

2

A-13

A.S0007-A v3.0 HRPD IOS

1 2

May 2007

6.1.10.2

A9-Connect-A8

This A9 interface message is sent from the PCF to the BS to complete the setup of the A8 connection.

Information Element A9 Message Type Call Connection Reference Correlation ID Mobile Identity (IMSI/ATI) Mobile Identity (ESN) CON_REF A8_Traffic_ID Cause PDSN IP Address Session State Information Record Section Reference Element Direction 6.2.2.167 6.2.2.98 6.2.2.108 6.2.2.16 6.2.2.16 6.2.2.168 6.2.2.170 6.2.2.19 6.2.2.30 6.2.2.202 PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS O Oa Od Ob Oe O Oc Of Og Type M R C R C R R R R C

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

a. This element shall only be included if it was also included in the A9-Setup-A8 message. This element shall be set to the value received in that message. b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS. Use of the ESN in this message is a network operator decision. This information element shall not be included in HRPD messages. c. Allowable cause values are: "PCF resources not available"; "Equipment failure"; "Successful operation", "PDSN resources are not available", "Data ready to send". d.The PCF transmits its Access Network Identifiers (CANID) to the Base Station. d. The IMSI shall be included in 1x systems. In HRPD messages the revision 0 AN sets this information element to the MN ID associated with the A10 connection, otherwise, UATI32 is used. e. The IS-2000 CON_REF field of this information element shall be set to 00H for padding, in HRPD messages. f. The AN compliant to revision A or a later version shall set the IP Address field of this information element to 00 00 00 00H for padding.

g. This information element shall not be included in 1x systems. In HRPD messages, this information element shall be included when the PCF decides that session information needs to be transferred to the AN. Multiple copies of this information element may be included.

A-14

May 2007

1

A.S0007-A v3.0 HRPD IOS

The following table shows the bitmap layout for the A9-Connect-A8 message:

7 (MSB) (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> 4 5 6 7 8 9 (LSB) (MSB) Correlation ID: A3/A7 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 10 1 2 3 4 5 (LSB) Mobile Identity (IMSI): A1 Element Identifier = [0DH] Length = [06H-08H] (10-15 digits) Identity Digit 1 = [0H-9H] (BCD) Odd/even Indicator = [1,0] Type of Identity = [110 (IMSI), 111 (ATI)] 6 1 2 3

A9 Message Type = [02H] A1 Element Identifier = [3FH]

Call Connection Reference:

Length = [08H] Market ID = <any value>

Identity Digit 3 = [0H-9H] (BCD) Identity Digit N+1 = [0H-9H] (BCD) = [1111] (if even number of digits) History Ind = [0H (Current)] (MSB) (MSB)

Identity Digit 2 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD) ATI Type = [2H (UATI 32)] (LSB)

4 n n+1 4 5 6 7

UATIColorCode = <any value> UATI024 = <any value>

(LSB) -- Continued on next page --

8

A-15

A.S0007-A v3.0 HRPD IOS

1

May 2007

-- Continued from previous page - Mobile Identity (ESN): A1 Element Identifier = [0DH] Length = [05H] Identity Digit 1 = [0000] Odd/even Indicator = [0] ESN = <any value> Type of Identity = [101] (ESN) 1 2 3

(MSB)

4 5 6 (LSB) 7 1 2 3 1 2 3 4 (LSB) 5 6 7 8 (LSB) 9 10 11 12 13 (LSB) 14 1 2 3

CON_REF:

A9 Element Identifier = [01H]

Length = [01H] IS-2000 CON_REF = [00H ­ FFH] A8 Traffic ID: A9 Element Identifier = [08H]

Length = [0CH] A8 transport protocol stack = [01H] (GRE/IP) (MSB) (MSB) Protocol Type = [88 81H] (Unstructured byte stream) Key = <any value>

Address Type = [01H] (IPv4) (MSB) IP Address = <any value>

ext = [0]

Cause: A9 Element Identifier = [04H] Length = [01H] [13H (Successful operation), 20H (Equipment failure), 32H (PCF resources not available), 79H (PDSN resources are not available), 7AH (Data Ready to Send) ]

Cause Value =

(MSB)

PDSN IP Address: A1 Element Identifier = [14H] Length = [04H] PDSN IP Address = <any value>

1 2 3 4 5 (LSB) 6

-- Continued on next page --

A-16

May 2007

1

A.S0007-A v3.0 HRPD IOS

-- Continued from previous page - (MSB) (MSB) Session State Information Record: A14 Element Identifier = [8AH] 1 2

Length = [variable]

(LSB)

Session State Information Record (LSB)

2

3

4 n

A-17

A.S0007-A v3.0 HRPD IOS

1 2

May 2007

6.1.10.3

A9-Disconnect-A8

This A9 interface message is sent from the PCF to the BS to release the associated dedicated resource.

Information Element A9 Message Type Call Connection Reference Correlation ID Mobile Identity (IMSI/ATI) Mobile Identity (ESN) CON_REF A8_Traffic_ID Cause Section Reference Element Direction 6.2.2.167 6.2.2.98 6.2.2.108 6.2.2.16 6.2.2.16 6.2.2.168 6.2.2.170 6.2.2.19 PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS O Oa Od Ob Oe O Oc Type M R C R C R R R

3 4 5 6 7 8 9 10 11 12 13

a. If this element is included in this message, its value shall be returned in the corresponding element in the A9-Release-A8 message sent in response to this message. b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS. Use of the ESN in this message is a network operator decision. This information element shall not be included in HRPD messages. c. Allowable cause values are: "Packet call going dormant"; "Equipment failure"; "Normal call release". d. The IMSI shall be included in 1x systems. In HRPD messages the revision 0 AN sets this information element to the MN ID associated with the A10 connection, otherwise, UATI32 is used. e. The IS-2000 CON_REF field of this information element shall be set to 00H for padding, in HRPD messages.

A-18

May 2007

1

A.S0007-A v3.0 HRPD IOS

The following table shows the bitmap layout for the A9-Disconnect-A8 message:

7 (MSB) (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> 4 5 6 7 8 9 (LSB) (MSB) Correlation ID: A3/A7 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 10 1 2 3 4 5 (LSB) Mobile Identity (IMSI): A1 Element Identifier = [0DH] Length = [06H-08H] (10-15 digits) Identity Digit 1 = [0H-9H] (BCD) Odd/even Indicator = [1,0] Type of Identity = [110 (IMSI), 111 (ATI)] 6 1 2 3

A9 Message Type = [03H] A1 Element Identifier = [3FH]

Call Connection Reference:

Length = [08H] Market ID = <any value>

Identity Digit 3 = [0H-9H] (BCD) Identity Digit N+1 = [0H-9H] (BCD) = [1111] (if even number of digits) History Ind = [0H (Current)] (MSB) (MSB)

Identity Digit 2 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD) ATI Type = [2H (UATI 32)] (LSB)

4 n n+1 4 5 6 7

UATIColorCode = <any value> UATI024 = <any value>

(LSB) -- Continued on next page --

8

A-19

A.S0007-A v3.0 HRPD IOS

1

May 2007

-- Continued from previous page - Mobile Identity (ESN): A1 Element Identifier = [0DH] Length = [05H] Identity Digit 1 = [0000] Odd/even Indicator = [0] ESN = <any value> Type of Identity = [101] (ESN) 1 2 3

(MSB)

4 5 6 (LSB) 7 1 2 3 1 2 3 4 (LSB) 5 6 7 8 (LSB) 9 10 11 12 13 (LSB) 14 1 2 3

CON_REF:

A9 Element Identifier = [01H]

Length = [01H] IS-2000 CON_REF = [00H ­ FFH] A8 Traffic ID: A9 Element Identifier = [08H]

Length = [0CH] A8 transport protocol stack = [01H] (GRE/IP) (MSB) (MSB) Protocol Type = [88 81H] (Unstructured byte stream) Key = <any value>

Address Type = [01H] (IPv4) (MSB) IP Address = <any value>

ext = [0]

Cause: A9 Element Identifier = [04H] Length = [01H] [10H (Packet call going dormant), 14H (Normal call release), 20H (Equipment failure) ]

Cause Value =

2

A-20

May 2007

1 2

A.S0007-A v3.0 HRPD IOS A9-Release-A8

6.1.10.4

This A9 interface message is sent from the BS to the PCF to release the associated dedicated resource.

Information Element A9 Message Type Call Connection Reference Correlation ID Mobile Identity (IMSI/ATI) Mobile Identity (ESN) CON_REF A8_Traffic_ID Cause Active Connection Time in Seconds Sector ID Session State Information Record Section Reference Element Direction 6.2.2.167 6.2.2.98 6.2.2.108 6.2.2.16 6.2.2.16 6.2.2.168 6.2.2.170 6.2.2.19 6.2.2.11 6.2.2.198 6.2.2.202 BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF O Oa Oe Ob Of O Oc Od Og Oh Type M R C R C R R R R C C

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

a. This element shall be included if it was also included in the A9-Disconnect-A8 message. This element shall be set to the value received in that message. If this element was not included in that message, it may be included in this message. b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS. Use of the ESN in this message is a network operator decision. This information element shall not be included in HRPD messages. c. Allowable cause values are: "Packet call going dormant"; "Equipment failure"; "Normal call release"; "Handoff successful"; "Authentication failure" and "Air link lost". Note that Normal call release indicates that the service has been released and therefore the A10 resources should be dropped. d. This element shall be included to indicate the active connection time for a traffic channel. e. The IMSI shall be included in 1x systems. In HRPD messages the revision 0 AN sets this information element to the MN ID associated with the A10 connection, otherwise, UATI32 is used. f. The IS-2000 CON_REF field of this information element shall be set to 00H for padding, in HRPD messages.

g. This information element shall not be included in 1x systems. h. Multiple copies of this information element may be included. This information element shall not be included in 1x systems.

A-21

A.S0007-A v3.0 HRPD IOS

1

May 2007

The following table shows the bitmap layout for the A9-Release-A8 message:

7 (MSB) (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> 4 5 6 7 8 9 (LSB) (MSB) Correlation ID: A3/A7 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 10 1 2 3 4 5 (LSB) Mobile Identity (IMSI/ATI)): A1 Element Identifier = [0DH] Length = [06H-08H] (10-15 digits) Identity Digit 1 = [0H-9H] (BCD) Odd/even Indicator = [1,0] Type of Identity = [110 (IMSI), 111 (ATI)] 6 1 2 3

A9 Message Type = [04H] A1 Element Identifier = [3FH]

Call Connection Reference:

Length = [08H] Market ID = <any value>

Identity Digit 3 = [0H-9H] (BCD) Identity Digit N+1 = [0H-9H] (BCD) = [1111] (if even number of digits) History Ind = [0H (Current)] (MSB) (MSB)

Identity Digit 2 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD) ATI Type = [2H (UATI 32)] (LSB)

4 n n+1 4 5 6 7

UATIColorCode = <any value> UATI024 = <any value>

(LSB) -- Continued on next page --

8

A-22

May 2007

1

A.S0007-A v3.0 HRPD IOS

-- Continued from previous page - Mobile Identity (ESN): A1 Element Identifier = [0DH] Length = [05H] Identity Digit 1 = [0000] Odd/even Indicator = [0] ESN = <any value> Type of Identity = [101] (ESN) 1 2 3

(MSB)

4 5 6 (LSB) 7 1 2 3 1 2 3 4 (LSB) 5 6 7 8 (LSB) 9 10 11 12 13 (LSB) 14 1 2 3

CON_REF:

A9 Element Identifier = [01H]

Length = [01H] IS-2000 CON_REF = [00H ­ FFH] A8 Traffic ID: A9 Element Identifier = [08H]

Length = [0CH] A8 transport protocol stack = [01H] (GRE/IP) (MSB) (MSB) Protocol Type = [88 81H] (Unstructured byte stream) Key = <any value>

Address Type = [01H] (IPv4) (MSB) IP Address = <any value>

ext = [0]

Cause: A9 Element Identifier = [04H] Length = [01H] [10H (Packet call going dormant), 14H (Normal call release), 0BH (Handoff successful), 20H (Equipment failure), 1AH (Authentication failure) 1FH (Air link lost) ] -- Continued on next page --

Cause Value =

A-23

A.S0007-A v3.0 HRPD IOS

1

May 2007

-- Continued from previous page - (MSB) Active Connection Time in Seconds: Length = [04H] Active Connection Time = [00 00 00 00H ­ FF FF FF FFH] A9 Element Identifier = [0AH] 1 2 3 4 5 (LSB) Sector ID: A14 Element Identifier = [88H] Length = [11H] SectorID Discriminator = [01H (SectorID128)] (MSB) Sector ID = <any value> 6 1 2 3 4 5 (LSB) (MSB) (MSB) Session State Information Record: A14 Element Identifier = [8AH] 19 1 2

Length = [variable]

(LSB)

Session State Information Record (LSB)

2 3

3

4 n

A-24

May 2007

1 2 3

A.S0007-A v3.0 HRPD IOS A9-Release-A8 Complete

6.1.10.5

This A9 interface message is sent from the PCF to the BS to acknowledge completion of the request to release the connection.

Information Element A9 Message Type Call Connection Reference Correlation ID Cause Mobile Identity (ATI) Session State Information Record HRPD A9 Indicators Section Reference Element Direction 6.2.2.167 6.2.2.98 6.2.2.108 6.2.2.19 6.2.2.16 6.2.2.202 6.2.2.201 PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS BS -> PCF M O Oa Ob Oc Od Oe R C C C C C Type

4 5 6 7 8 9 10 11 12 13 14 15 16 17

a. This element shall only be included if it was also included in the A9-Release-A8 message. This element shall be set to the value received in that message. b. This element shall not be included if the connection was released due to packet call going dormant. Otherwise, this element shall be included. Allowable cause values are "PDSN resource unavailable" and "Packet Call going dormant". For HRPD systems, the following cause values are also allowed; "Authentication failure", "Authentication required", "PCF resources not available" and Equipment failure. c. In HRPD messages, the AN compliant to revision A or a later version shall include this information element. d. Multiple copies of this information element may be included. This information element shall not be included in 1x systems. e. This information element shall not be included in 1x systems. In HRPD messages, the PCF assumes that all indicators are set to `0' if this information element is not included in the message. The following table shows the bitmap layout for the A9-Release-A8 Complete message:

7 (MSB) (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> 4 5 6 7 8 9 (LSB) -- Continued on next page -10

A9 Message Type = [05H] A1 Element Identifier = [3FH]

Call Connection Reference:

Length = [08H] Market ID = <any value>

A-25

A.S0007-A v3.0 HRPD IOS

1

May 2007

-- Continued from previous page - (MSB) Correlation Value = <any value> (LSB) ext = [0] Cause: A9 Element Identifier = [04H] Length = [01H] Cause Value = [10H (Packet Call going dormant), 1AH (Authentication failure), 20H (Equipment failure), 23H (Authentication required), 24H (Session unreachable), 32H (PCF resources not available), 79H (PDSN Resource Unavailable)] A1 Element Identifier = [0DH] Odd/even Indicator = [0] Type of Identity = [110 (IMSI), 111 (ATI)] (LSB) Correlation ID: A3/A7 Element Identifier = [13H] Length = [04H] 1 2 3 4 5 6 1 2 3

Mobile Identity (ATI):

1 2 3

Length = [05H] Identity Digit 1 = [0000]

History Ind = [0H (Current)] (MSB) (MSB)

ATI Type = [2H (UATI 32)]

4 5 6 7 (LSB) 8 1 2

UATIColorCode = <any value> UATI24 = <any value>

(MSB) (MSB)

Session State Information Record:

A14 Element Identifier = [8AH]

Length = [variable]

(LSB)

Session State Information Record (LSB) HRPD A9 Indicators: Reserved = [0000 00] A9 Element Identifier = [8BH] Default Session Indicator = [0, 1] Session Informat ion Require d = [0]

3

4 n 1 2 3

Length = [01H]

2

A-26

May 2007 6.1.10.6 A9-BS Service Request

A.S0007-A v3.0 HRPD IOS

1 2

No changes from TIA/EIA/IS-2001-A text. 6.1.10.7 A9-BS Service Response

3 4

No changes from TIA/EIA/IS-2001-A text. 6.1.10.8 A9-AL Connected

5 6 7 8

This A9 interface message is sent from the BS to the PCF to indicate that the traffic channel is established when the MS performed Hard Handoff or in HRPD systems when the AN determines that data flow stopped by the A9-AL Disconnected message from the PCF should be resumed.

Information Element A9 Message Type Call Connection Reference Correlation ID A8_Traffic_ID PDSN IP Address IS-2000 Service Configuration Record Service option User Zone ID Quality of Service Parameters Access Network Identifiers Mobile Identity (ATI) Section Reference Element Direction 6.2.2.167 6.2.2.98 6.2.2.108 6.2.2.170 6.2.2.30 6.2.2.68 6.2.2.66 6.2.2.32 6.2.2.54 6.2.2.189 6.2.2.16 BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF O Oa O Of Oc O Od Oe Ob Og Type M R C R R R R R R

R

C

9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

a. If this element is included in this message, its value shall be returned in the corresponding element in the A9-AL Connected Ack message sent in response to this message. b. The Access Network Identifiers are those of the source PCF communicated by the source BSC via the MSC (handoff required, handoff requested messages), in 1x systems. In HRPD system, the AN compliant to revision A or a later version shall set SID, NID and PZID field to `0' respectively. c. The Bit-Exact Length ­ Octet Count field and the Bit-Exact Length ­ Fill Bits field of this information element shall set to `0', in HRPD messages. d. The UZID field of this information element shall be set to 00H for padding, in HRPD messages. e. The Non-Assured Mode Packet Priority field of this information element shall set to 0H for padding, in HRPD messages. f. The AN compliant to revision A or a later version shall set the IP Address field of this information element to 00 00 00 00H for padding.

g. This information element shall not be included in 1x systems. In HRPD messages, the AN compliant to revision A or a later version shall include this information element.

A-27

A.S0007-A v3.0 HRPD IOS

1

May 2007

The following table shows the bitmap layout for the A9-AL Connected message:

7 (MSB) (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> 4 5 6 7 8 9 (LSB) (MSB) Correlation ID: A3/A7 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 10 1 2 3 4 5 (LSB) A8 Traffic ID: A9 Element Identifier = [08H] 6 1 2 3 4 (LSB) (MSB) Key = <any value> 5 6 7 8 (LSB) Address Type = [01H] (IPv4) (MSB) IP Address = <any value> 9 10 11 12 13 (LSB) (MSB) PDSN IP Address: A1 Element Identifier = [14H] Length = [04H] PDSN IP Address = <any value> 14 1 2 3 4 5 (LSB) -- Continued on next page -6

A9 Message Type = [08H] A1 Element Identifier = [3FH]

Call Connection Reference:

Length = [08H] Market ID = <any value>

Length = [0CH] A8 transport protocol stack = [01H] (GRE/IP) (MSB) Protocol Type = [88 81H] (Unstructured byte stream)

A-28

May 2007

1

A.S0007-A v3.0 HRPD IOS

-- Continued from previous page - IS-2000 Service Configuration Record: A1 Element Identifier = [0EH] 1 2 Bit-Exact Length ­ Fill Bits = [000 to 111] 3 4 IS-2000 Service Configuration Record Content = <any value> Seventh Fill Bit ­ if needed = [0 (if used as a fill bit)] (MSB) (MSB) Sixth Fill Bit ­ if needed = [0 (if used as a fill bit)] Fifth Fill Bit ­ if needed = [0 (if used as a fill bit)] Fourth Fill Bit ­ if needed = [0 (if used as a fill bit)] Third Fill Bit ­ if needed = [0 (if used as a fill bit)] Second Fill Bit ­ if needed = [0 (if used as a fill bit)] First Fill Bit ­ if needed = [0 (if used as a fill bit)] ... k

Bit-Exact Length ­ Octet Count = [00H to FFH] Reserved = [0000 0] (MSB)

Service Option: A1 Element Identifier = [03H] Service Option = [ 00 3B H (High Rate Packet Data) ] User Zone ID: A1 Element Identifier = [02H] (LSB)

1 2 3 1 2 3 (LSB) 4 1 2 3 1 2 3 (LSB) 4 5 (LSB) 6 7 1 2 3 (LSB)

Length = [02H] UZID = <any value>

Quality of Service Parameters: Reserved = [0000]

A1 Element Identifier = [07H]

Length = [01H] Non-Assured Mode Packet Priority = [0000 ­ 1101]

ACCESS NETWORK IDENTIFIERS: A1 ELEMENT IDENTIFIER = [20H] Length = [05H] Reserved (MSB) (MSB) (MSB) SID = <any value> NID = <any value> PZID = <any value> Mobile Identity (ATI): A1 Element Identifier = [0DH] Odd/even Indicator = [0] Type of Identity = [111] (ATI)

Length = [05H] Identity Digit 1 = [0000]

History Ind = [0H (Current)] (MSB) (MSB)

ATI Type = [2H (UATI 32)] (LSB)

4 5 6 7 (LSB) 8

UATIColorCode = <any value> UATI24 = <any value>

A-29

A.S0007-A v3.0 HRPD IOS

1 2 3

May 2007

6.1.10.9

A9-AL Connected Ack

This A9 interface message is sent from the PCF to the BS to acknowledge completion of the processing of the A9-AL Connected message or the A9-AL Connected message for HRPD systems.

Information Element A9 Message Type Call Connection Reference Correlation ID PDSN IP Address Mobile Identity (ATI) Section Reference Element Direction 6.2.2.167 6.2.2.98 6.2.2.108 6.2.2.30 6.2.2.16 PCF -> BS PCF -> BS PCF -> BS PCF -> BS PCF -> BS O Oa Ob Oc Type M R C C C

4 5 6 7 8 9 10

a. This element shall only be included if it was also included in the A9-AL Connected message. This element shall be set to the value received in that message. b. This IE may be included if the target PCF could not connect to the PDSN designated in the A9-AL Connected message. The AN compliant to revision A or a later version shall not include this information element. c. This information element shall not be included in 1x systems. In HRPD messages, the AN compliant to revision A or a later version shall set this information element. The following table shows the bitmap layout for the A9-AL Connected Ack message:

7 (MSB) (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> 4 5 6 7 8 9 (LSB) (MSB) Correlation ID: A3/A7 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 10 1 2 3 4 5 (LSB) -- Continued on next page -6

11

A9 Message Type = [09H] A1 Element Identifier = [3FH]

Call Connection Reference:

Length = [08H] Market ID = <any value>

A-30

May 2007

1

A.S0007-A v3.0 HRPD IOS

-- Continued from previous page - (MSB) PDSN IP Address: A1 Element Identifier = [14H] Length = [04H] PDSN IP Address = <any value> 1 2 3 4 5 (LSB) Mobile Identity (ATI): A1 Element Identifier = [0DH] Odd/even Indicator = [0] Type of Identity = [111] (ATI) 6 1 2 3

Length = [05H] Identity Digit 1 = [0000]

History Ind = [0H (Current)] (MSB) (MSB)

ATI Type = [2H (UATI 32)] (LSB)

4 5 6 7 (LSB) 8

UATIColorCode = <any value> UATI24 = <any value>

2 3

A-31

A.S0007-A v3.0 HRPD IOS

1 2 3 4

May 2007

6.1.10.10

A9-AL Disconnected

This A9 interface message is sent from the BS to the PCF to indicate that the traffic channel is to be released when the MS performed Hard Handoff or in HRPD systems when the AN determines that data flow from the PCF should be stopped.

Information Element A9 Message Type Call Connection Reference Correlation ID A8_Traffic_ID Mobile Identity (ATI) Section Reference Element Direction 6.2.2.167 6.2.2.98 6.2.2.108 6.2.2.170 6.2.2.16 BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF M O Oa O Ob R C R C Type

5 6 7 8 9

a. If this information element is included in this message, its value shall be returned in the corresponding information element in the A9-AL Disconnected Ack message sent in response to this message. b. This information element shall not be included in 1x systems. In HRPD messages, the AN compliant to revision A or a later version shall set this information element. The following table shows the bitmap layout for the A9-AL Disconnected message:

7 6 5 4 3 2 1 0 Octet 1 1 2

A9 Message Type = [0AH] A1 Element Identifier = [3FH]

Call Connection Reference:

Length = [08H] -- Continued on next page --

A-32

May 2007

1

A.S0007-A v3.0 HRPD IOS

-- Continued from previous page -(MSB) (MSB) (MSB) Market ID = <any value> (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> 3 4 5 6 7 8 9 (LSB) (MSB) Correlation ID: A3/A7 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 10 1 2 3 4 5 (LSB) A8 Traffic ID: A9 Element Identifier = [08H] 6 1 2 3 4 (LSB) (MSB) Key = <any value> 5 6 7 8 (LSB) Address Type = [01H] (IPv4) (MSB) IP Address = <any value> 9 10 11 12 13 (LSB) Mobile Identity (ATI): A1 Element Identifier = [0DH] Odd/even Indicator = [0] Type of Identity = [111] (ATI) 14 1 2 3

Length = [0CH] A8 transport protocol stack = [01H] (GRE/IP) (MSB) Protocol Type = [88 81H] (Unstructured byte stream)

Length = [05H] Identity Digit 1 = [0000]

History Ind = [0H (Current)] (MSB) (MSB)

ATI Type = [2H (UATI 32)] (LSB)

4 5 6 7 (LSB) 8

UATIColorCode = <any value> UATI24 = <any value>

2 3

A-33

A.S0007-A v3.0 HRPD IOS

1 2 3 4

May 2007

6.1.10.11

A9-AL Disconnected Ack

For 1x systems, this This A9 interface message is sent from the PCF to the BS to acknowledge the reception of the A9-AL Disconnect message. For HRPD systems, the A9-AL Disconnected Ack message is only used to acknowledge the A9-AL Disconnected message.

Information Element A9 Message Type Call Connection Reference Correlation ID Mobile Identity (ATI) Section Reference Element Direction 6.2.2.167 6.2.2.98 6.2.2.108 6.2.2.16 PCF -> BS PCF -> BS PCF -> BS PCF -> BS O Oa Ob Type M R C C

5 6 7 8

a. This element shall only be included if it was also included in the A9-AL Disconnected message. This element shall be set to the value received in that message. b. This information element shall not be included in 1x systems. In HRPD messages, the AN compliant to revision A or a later version shall set this information element. The following table shows the bitmap layout for the A9-AL Disconnected Ack message:

7 (MSB) (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> 4 5 6 7 8 9 (LSB) (MSB) Correlation ID: A3/A7 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 10 1 2 3 4 5 (LSB) -- Continued on next page -6 A9 Message Type = [0BH] A1 Element Identifier = [3FH]

9

Call Connection Reference:

Length = [08H] Market ID = <any value>

A-34

May 2007

1

A.S0007-A v3.0 HRPD IOS

-- Continued from previous page - Mobile Identity (ATI): A1 Element Identifier = [0DH] Odd/even Indicator = [0] Type of Identity = [111] (ATI) 1 2 3

Length = [05H] Identity Digit 1 = [0000]

History Ind = [0H (Current)] (MSB) (MSB)

ATI Type = [2H (UATI 32)] (LSB)

4 5 6 7 (LSB) 8

UATIColorCode = <any value> UATI24 = <any value>

2 3 4 5 6

6.1.10.12

A9-Short Data Delivery

This message is sent from the BS to the PCF when a short data burst is received from a mobile. It is sent from the PCF to the BS when a small amount of data is received for a mobile when it's packet data service instance is dormant. This section is not applicable to HRPD systems.

Information Element A9 Message Type Correlation ID Mobile Identity (IMSI) Mobile Identity (ESN) SR_ID Data Count ADDS User Part Section Reference Element Direction 6.2.2.167 6.2.2.108 6.2.2.16 6.2.2.16 6.2.2.26 6.2.2.179 6.2.2.67 PCF <-> BS PCF->BS PCF <-> BS BS <-> PCF BS<->PCF PCF->BS PCF <-> BS Oa O Ob O Oc Od Type M C R C R C R

7 8 9 10 11 12 13 14 15

a. If this element is included, its value shall be returned in the corresponding element in the A9-Short Data Ack message from the BS. b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS. Use of the ESN in this message is a network operator decision. c. This element is included in this message when sent from the PCF to the BS and indicates the number of additional bytes of data queued at the PCF and waiting to be sent to a specific mobile. d. Contains the packet data received from the PDSN or an MS in a SDB format as specified in IS-707A-2.

A-35

A.S0007-A v3.0 HRPD IOS

1

May 2007

The following table shows the bitmap layout for the A9-Short Data Delivery message.

7 6 (MSB) 5 4 3 2 1 0 Octet 1 1 2 3 4 5 (LSB) Mobile Identity (IMSI): A9 Element Identifier = [0DH] Length = [06H-08H] (10-15 digits) Identity Digit 1 = [0H-9H] (BCD) Odd/even Indicator = [1,0] Type of Identity = [110] (IMSI) 6 1 2 3 A9 Message Type = [0CH]

Correlation ID: A8/A9 Element Identifier = [13H] Length = [04H] Correlation Value = <any value>

Identity Digit 3 = [0H-9H] (BCD) Identity Digit N+1 = [0H-9H] (BCD) = [1111] (if even number of digits)

Identity Digit 2 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD)

4 n n+1 1 2 3

Mobile Identity (ESN): A1 Element Identifier = [0DH] Length = [05H] Odd/even Indicator = [0] ESN = <any value> Type of Identity = [101] (ESN)

Identity Digit 1 = [0000]

(MSB)

4 5 6 (LSB) 7 1 2 IS-2000 SR_ID = [001 - 011] 3 1 2 3 4 1 2 3 4 (LSB) n

SR_ID: A9 Element Identifier = [0BH] Length = [01H]

Reserved = [0000 0] Data Count:

A9 Element Identifier = [09H]

Length = [02H] Count = <any value> ... Reserved = [00] (MSB) ADDS User Part: A1 Element Identifier = [3DH] Data Burst Type = [ 06H (Short Data Burst) ] Application Data Message = <any value>

Length = <variable>

2

A-36

May 2007

1 2 3 4 5

A.S0007-A v3.0 HRPD IOS A9-Short Data Ack

6.1.10.13

This A9 interface message is sent from the BS to the PCF to acknowledge reception of the A9-Short Data Delivery message and to indicate to the PCF whether the data was accepted for delivery to the mobile. This section is not applicable to HRPD systems.

Information Element A9 Message Type Correlation ID Mobile Identity (IMSI) Mobile Identity (ESN) SR_ID Cause Section Reference 6.2.2.167 6.2.2.108 6.2.2.16 6.2.2.16 6.2.2.26 6.2.2.19 Element Direction BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF Oa O Ob O Oc Type M C R C R R

6 7 8 9 10 11 12

a. If this element is included, its value shall be set to the value of the corresponding element in the A9Short Data Delivery message from the PCF. b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS. Use of the ESN in this message is a network operator decision. c. The cause value indicates to the PCF whether a short data burst be sent to the mobile. The following table shows the bitmap layout for the A9-Short Data Ack message.

7 6 (MSB) 5 4 3 2 1 0 Octet 1 1 2 3 4 5 (LSB) Mobile Identity (IMSI): A9 Element Identifier = [0DH] Length = [06H-08H] (10-15 digits) Identity Digit 1 = [0H-9H] (BCD) Odd/even Indicator = [1,0] Type of Identity = [110] (IMSI) 6 1 2 2 A9 Message Type = [0DH]

Correlation ID: A8/A9 Element Identifier = [13H] Length = [04H] Correlation Value = <any value>

Identity Digit 3 = [0H-9H] (BCD) Identity Digit N+1 = [0H-9H] (BCD) = [1111] (if even number of digits)

Identity Digit 2 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD)

3 n n+1 1 2

Mobile Identity (ESN): A1 Element Identifier = [0DH] Length = [05H] -- Continued on next page --

A-37

A.S0007-A v3.0 HRPD IOS

1

May 2007

-- Continued from previous page -Identity Digit 1 = [0000] Odd/even Indicator = [0] ESN = <any value> Type of Identity = [101] (ESN) 3

(MSB)

4 5 6 (LSB) 7 1 2 IS-2000 SR_ID = [001 - 011] 3 1 2 3

SR_ID: A9 Element Identifier = [0BH] Length = [01H]

Reserved = [0000 0] ext = [0]

Cause: A1 Element Identifier = [04H] Length = [01H] [13H (Successful Operation), 16H (Initiate Re-activation of Packet Data call)]

Cause Value =

2 3 4 5

6.1.10.14

A9-Update-A8

This A9 interface message is sent from the BS to the PCF to indicate a change to the session airlink parameters.

Information Element A9 Message Type Call Connection Reference Correlation ID Mobile Identity (IMSI) Mobile Identity (ESN) IS-2000 Service Configuration Record Service Option User Zone ID Quality of Service Parameters Cause Section Reference Element Direction 6.2.2.167 6.2.2.98 6.2.2.108 6.2.2.16 6.2.2.16 6.2.2.68 6.2.2.66 6.2.2.32 6.2.2.54 6.2.2.19 BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF BS -> PCF O Oa Od Ob,c Oc,e Oc Oc Oc,e O Type M R C R C C C C C R

6 7 8 9 10 11 12 13 14

a. If this element is included in this message, its value shall be returned in the corresponding element in the A9-Update-A8-Ack message sent in response to this message. b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS. Use of the ESN in this message is a network operator decision. c. These elements are required unless the message is used to indicate Dormant Power down or Authentication Failure. d. This information element shall be set to the MN ID, retrieved from AN-AAA, in HRPD messages. e. This information element shall not be included in HRPD messages.

A-38

May 2007

1

A.S0007-A v3.0 HRPD IOS

The following table shows the bitmap layout for the A9-Update-A8 message:

7 (MSB) (MSB) (MSB) 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> 4 5 6 7 8 9 (LSB) (MSB) Correlation ID: A3/A7 Element Identifier = [13H] Length = [04H] Correlation Value = <any value> 10 1 2 3 4 5 (LSB) Mobile Identity (IMSI): A9 Element Identifier = [0DH] Length = [06H-08H] (10-15 digits) Identity Digit 1 = [0H-9H] (BCD) Odd/even Indicator = [1,0] Type of Identity = [110] (IMSI) 6 1 2 2 A9 Message Type = [03H] A1 Element Identifier = [3FH]

Call Connection Reference:

Length = [08H] Market ID = <any value>

Identity Digit 3 = [0H-9H] (BCD) Identity Digit N+1 = [0H-9H] (BCD) = [1111] (if even number of digits)

Identity Digit 2 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD)

3 n n+1 1 2 3

Mobile Identity (ESN): A1 Element Identifier = [0DH] Length = [05H] Odd/even Indicator = [0] ESN = <any value> Type of Identity = [101] (ESN)

Identity Digit 1 = [0000]

(MSB)

4 5 6 (LSB) 7

-- Continued on next page --

A-39

A.S0007-A v3.0 HRPD IOS

1

May 2007

-- Continued from previous page - IS-2000 Service Configuration Record: Reserved = [ 0000 0 ] (MSB) IS-2000 Service Configuration Record Content = <any value> Seventh Fill Bit ­ if needed = [0 (if used as a fill bit)] (MSB) (MSB) Sixth Fill Bit ­ if needed = [0 (if used as a fill bit)] Fifth Fill Bit ­ if needed = [0 (if used as a fill bit)] Fourth Fill Bit ­ if needed = [0 (if used as a fill bit)] Third Fill Bit ­ if needed = [0 (if used as a fill bit)] Second Fill Bit ­ if needed = [0 (if used as a fill bit)] First Fill Bit ­ if needed = [0 (if used as a fill bit)] A1 Element Identifier = [0EH] Bit-Exact Length ­ Fill Bits = [ 000 ­ 111 ] 1 2 3 4 ... k

Bit-Exact Length ­ Octet Count = <variable>

Service Option: A1 Element Identifier = [03H] Service Option = [ 00 3B H (High Rate Packet Data ) ] User Zone ID: A1 Element Identifier = [02H] (LSB)

1 2 3 1 2 3 (LSB) 4 1 2 3 1 2 3

Length = [02H] UZID = <any value>

Quality of Service Parameters: Reserved = [0000]

A1 Element Identifier = [07H]

Length = [01H] Non-Assured Mode Packet Priority = [0000 ­ 1101] Cause: A1 Element Identifier = [04H] Length = [01H] Ext= [0] Cause Value = [19H (Power down from dormant state), 1CH (update accounting: late traffic channel setup), 1EH (update accounting: parameter change), 1AH (Authentication Failure)]

2 3 4

6.1.10.15

A9-Update-A8-Ack

No changes from TIA/EIA/IS-2001-A text.

A-40

May 2007

1 2 3 4 5 6 7

A.S0007-A v3.0 HRPD IOS

6.2.1

Generic Information Element Encoding

6.2.1.2 Information Element Identifiers The following tables contain lists of all elements that make up the messages defined in section 6.1. The tables include the Information Element Identifier (IEI) coding which distinguishes one element from another. The tables also include a section and page reference where the element coding can be found. ··· Table 6.2.1.2-5 - A9 Information Element Identifiers Sorted by Identifier Name

Element Name A8 Traffic ID A9 BSC_ID A9 Indicators Access Network Identifiers Active Connection Time in Seconds Call Connection Reference Cause CON_REF Correlation ID Data Count HRPD A9 Indicators Mobile Identity Quality of Service Parameters PDSN IP Address Sector ID Security Layer Packet Service Option Session State Information Record SR_ID System Time User Zone ID Identifier 08H 06H 05H 20H 0AH 3FH 04H 01H 13H 09H 8BH 0DH 07H 14H 88H 89H 03H 8AH 0BH 8CH 02H Interface(s) A9 A9 A9 A1, A9 A9 A3, A7, A9 A1, A7, A9 A9 A3, A7, A9 A9 A9 A1, A7, A9 A1, A7, A9 A1, A9 A9 A9 A9 A9

a a

Reference 6.2.2.170 6.2.2.169 6.2.2.171 6.2.2.189 6.2.2.11 6.2.2.98 6.2.2.19 6.2.2.168 6.2.2.108 6.2.2.179 6.2.2.201 6.2.2.16 6.2.2.54 6.2.2.30 6.2.2.198 6.2.2.199 6.2.2.66 6.2.2.202 6.2.2.26 6.2.2.200 6.2.2.32

A1, A9

a

A9

a

A1, A9

8 9 10

a. This information element is also used on the HRPD revision A interface.

Table 6.2.1.2-6 - A9 Information Element Identifiers Sorted by Identifier Value

Element Name CON_REF User Zone ID Service Option Cause A9 Indicators A9 BSC_ID Quality of Service Parameters A8 Traffic ID Identifier 01H 02H 03H 04H 05H 06H 07H 08H Interface(s) A9 A1, A9 A1, A9 A1, A9 A9 A9 A1, A9 A9 Reference 6.2.2.168 6.2.2.66 6.2.2.66 6.2.2.19 6.2.2.171 6.2.2.169 6.2.2.54 6.2.2.170

A-41

A.S0007-A v3.0 HRPD IOS

Element Name Data Count Active Connection Time in Seconds SR_ID Mobile Identity Correlation ID PDSN IP Address Access Network Identifiers Call Connection Reference Sector ID Security Layer Packet Session State Information Record HRPD A9 Indicators System Time

1

May 2007

Identifier 09H 0AH 0BH 0DH 13H 14H 20H 3FH 88H 89H 8AH 8BH 8CH Interface(s) A9 A9 A9 A1, A7, A9 A3, A7, A9 A1, A9 A1, A9 A3, A7, A9 A9

a

Reference 6.2.2.179 6.2.2.11 6.2.2.26 6.2.2.16 6.2.2.108 6.2.2.30 6.2.2.189 6.2.2.98

A9 a A9 a A9 A9 a

6.2.2.198 6.2.2.199 6.2.2.202 6.2.2.201

6.2.2.200

a. This information element is also used on the HRPD revision A interface. 6.2.2.16 Mobile Identity

2 3 4 5 6 7 8 9 10 11 12

The purpose of the mobile identity information element is to provide the mobile station Electronic Serial Number (ESN), the International Mobile Subscriber Identity (IMSI), or the Broadcast Address. The International Mobile Subscriber Identifier (IMSI) does not exceed 15 digits and the ESN is a 32 bit field separated into a Manufacturer code, the Serial Number and a Reserved field. The Broadcast Address is used to deliver Short Messages to groups of subscribers and has the format specified in section 3.4.3.2 of TIA/EIA/IS-637-A and is mapped to the Mobile Identity element as shown below. The following is the Mobile Identity element coding: TIA/EIA/IS-2000. Warning: The length limit for this information element was 10 octets in IOS v2.0a, IOS v2.1, and IOS v3.0.0. Care needs to be exercised for interoperability with implementations based on the previous standard.

7 6 5 4 Length Identity Digit 1 Identity Digit 3 Odd/even Indicator Type of Identity Identity Digit 2 3 2 1 0 Octet 1 2 3 4 ... Identity Digit N k A1 Element Identifier

...

Identity Digit N+1

13 14 15

The Length field is defined as the number of octets following the Length field. The Type of Identity is defined as follows:

A-42

May 2007

1

A.S0007-A v3.0 HRPD IOS

Table 6.2.2.16-1 - Mobile Identity - Type of Identity Coding Binary Values 000 010 101 110 111 Meaning No Identity Code Broadcast Address ESN IMSI ATI

2 3 4 5 6 7 8 9 10

The Odd/Even Indicator (octet 3; bit 3) field is set to `0' for an even number of digits and to `1' for an odd number of identity digits. The identity digits (octet 3 etc.) are coded as follows: The International Mobile Subscriber Identifier fields are coded using BCD coding format. If the number of identity digits is even then bits 4 to 7 of the last octet shall be filled with an end mark coded as `1111'. The ESN is not separated into digits, and occupies octets 4-7 with the most significant bit in octet 4 bit 7. Identity Digit 1 in octet 3 is unused and coded as `0000'. For Broadcast Address (Type 010), the Mobile Identity is either encoded as specified below, based on TIA/EIA/IS-637-A:

7 6 5 4 Length Reserved Priority Zone ID (MSB) Service (LSB) Language Message ID Type of Identity 3 2 1 0 Octet 1 2 3 4 5 6 7 8 A1 Element Identifier

11 12 13 14 15 16 17 18 19 20 21 22 23

Length: Type of Identity: Priority: Message ID:

This field indicates the number of octets in this element following the Length field. This field is defined as shown above. This field indicates the priority level of this broadcast message to the MS. This field contains a value used by the MS to distinguish between different messages from the same broadcast service transmitted within the time period established for broadcast duplicate detection in the mobile station. This field contains a value used by the MS to distinguish between messages from the same broadcast service transmitted in different geographic regions. This field contains the service category. The mobile station should receive and process the broadcast message or page if the Service field contains a service category that the mobile station has been configured to receive. This field contains a value used by the MS to distinguish the language used in the content of the broadcast message.

Zone ID: Service:

Language:

A-43

A.S0007-A v3.0 HRPD IOS

1

May 2007

Or the Mobile Identity is encoded as follows, for Access Terminal Identifiers:

7 6 5 4 Length Identity Digit 1 = [0000] Odd/even Indicator = [0] UATIColorCode UATI24 (LSB) Type of Identity 3 2 1 0 Octet 1 2 3 A1 Element Identifier

History Ind = [0H (Current)] (MSB) (MSB)

ATI Type = [2H (UATI 32)] (LSB)

4 5 6 7 8

2 3 4 5 6 7

Length: Type of Identity: UATIColorCode: UATI24: 6.2.2.19

This field indicates the number of octets in this information element following the Length field. This field is defined as shown above. UATI Color Code. This field to the Color Code associated with the subnet to which the UATI belongs. This field contains the lower 24 bits of the UATI already assigned to the AT. Cause

8

9 10

This element is used to indicate the reason for occurrence of a particular event and is coded as shown below.

7 6 5 4 Length 0/1 Cause Value 3 2 1 0 Octet 1 2 3 Element Identifier

11 12 13 14 15 16 17 18 19

This information element is used on multiple interfaces. When the information element is included in a message that is sent on the A1 or A9 interface, the Element Identifier field is coded as 04H. When the information element is included in a message sent on the A7 interface, the Element Identifier field is coded as 08H. The Length field is defined as the number of octets following the Length field. The Cause Value field is a single octet field if the extension bit (bit 7) is set to `0'. If bit 7 of octet 3 is set to `1' then the Cause Value is a two octet field. If the value of the first octet of the cause field is `1XXX 0000' then the second octet is reserved for national applications, where `XXX' indicates the Cause Class as indicated in the table below. Table 6.2.2.19-1 - Cause Class Values

Binary Values 000 001 010 011 100 Meaning Normal Event Normal Event Resource Unavailable Service or option not available Service or option not implemented

20

A-44

May 2007

Binary Values 101 110 111

1

A.S0007-A v3.0 HRPD IOS

Meaning Invalid message (e.g., parameter out of range) Protocol error Interworking

Table 6.2.2.19-2 - Cause Values

6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 2 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 1 0 Hex Value Cause Normal Event Class (000 xxxx and 001 xxxx) 0 0 00 Radio interface message failure 0 1 01 Radio interface failure 1 0 02 Uplink Quality 1 1 03 Uplink strength 0 0 04 Downlink quality 0 1 05 Downlink strength 1 0 06 Distance 1 1 07 OAM&P intervention 0 0 08 MS busy 0 1 09 Call processing 1 0 0A Reversion to old channel 1 1 0B Handoff successful 0 0 0C No response from MS 0 1 0D Timer expired 1 0 0E Better cell (power budget) (Handoff Required msg.) 1 1 0F Interference (Handoff Required msg.) 0 0 10 Packet call going dormant 0 1 11 Service option not available 1 0 12 Invalid Call 1 1 13 Successful operation 0 0 14 Normal call release 0 1 15 Short Data Burst Authentication Failure 1 0 16 Initiate Re-activation of packet data call 1 1 17 Time Critical Relocation/Handoff 0 0 18 Network Optimization 0 1 19 Power down from Dormant State 1 0 1A Authentication Failure 1 1 1B Inter-BS Soft Handoff Drop Target 0 0 1C Update Accounting: Late Traffic Channel Setup 0 1 1D Intra-BS Soft Handoff Drop Target 1 0 1E Update Accounting: Parameter Change 1 1 1F Air link lost Resource Unavailable Class (010 xxxx) 0 0 20 Equipment failure 0 1 21 No radio resource available 1 0 22 Requested terrestrial resource unavailable 1 1 23 Authentication required 0 0 24 Session unreachable 0 1 25 BS not equipped 1 0 26 MS not equipped (or incapable) 1 1 27 2G Only Sector 0 0 28 2G Only Carrier

2

A-45

A.S0007-A v3.0 HRPD IOS

1

May 2007 Table 6.2.2.19-2 - Cause Values (cont.)

6 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

5 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1

4 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 0 0 1

3 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1 0 0

2 0 0 0 1 1 0 0 0 0 1 1 0 0 0 0 1 1 0 0 1 1 0 0

Cause PACA Call Queued Invalid Session Information Alternate signaling type reject (Handoff Failure msg.) 0 1 2D PACA Queue Overflow 1 0 2E PACA Cancel Request Rejected Service or Option Not Available Class (011 xxxx) 0 0 30 Requested transcoding/rate adaptation unavailable 0 1 31 Lower priority radio resources not available 1 0 32 PCF resources not available 1 1 33 TFO Control request Failed 0 0 34 MS Rejected Order 0 1 35 Requested FPC Mode Change Failed Service or Option Not Implemented Class (100 xxxx) 0 0 40 Ciphering algorithm not supported 0 1 41 Private Long Code not available or not supported. 1 0 42 Requested MUX option or rates not available. 1 1 43 Requested Privacy Configuration unavailable 0 0 44 SCH not supported 1 1 4F Terrestrial circuit already allocated.a 29 2A 2B 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 1 1 1 0 1 0 1 0 1 0 1 0 1 0 1 Invalid Message Class (101 xxxx) 50 Terrestrial circuit already allocated 51 FPC Initial Gain too high 5F Protocol Error between BS and MSC.a 6F Invalid Call Connection Reference Protocol Error (110 xxxx) 60 Protocol Error between BS and MSC Interworking (111 xxxx) 71 ADDS message too long for delivery on the paging channel 72 MS-to-IWF TCP connection failure 73 ATH0 (Modem hang up) Command 74 +FSH/+FHNG (Fax session ended) Command 75 No carrier 76 PPP protocol failure 77 PPP session closed by the MS 78 Do not notify MS 79 PDSN resources are not available 7A Data ready to send 7F Handoff procedure time-out (HO Failure message) Reserved for future use.

1 0 1 1

0 1 0 1

Hex Value

1 0 0 1 0 0 1 0 1 1 0 1 1 0 1 1 0 1 1 1 0 1 1 0 1 1 0 1 1 1 All other values

2 3 4 5 6 7 8

a. Used prior to version 3.0.0 of this specification only. If The MSC uses a CIC value that is unknown to the BS, the cause value used shall be 25H (BS not equipped) in the appropriate message. 6.2.2.167 A9 Message Type No changes from TIA/EIA/IS-2001-A text.

A-46

May 2007

1 2

A.S0007-A v3.0 HRPD IOS Sector ID 0 Octet 1 2 3 4 5 (LSB) 19

6.2.2.198

This information element is set to the sector identifier associated with the AT. 7 6 5 4 3 2 1 A9 Element Identifier = [88H] Length SectorID Discriminator (MSB) Sector ID

3 4

Length SectorID Discriminator Sector ID 6.2.2.199

This field shall be set to the length of this information element in octets following the Length Field. This field indicates SectorID Discriminator. This field is set to the 128-bit address of the sector. Security Layer Packet Octet 1 2 3 4 (LSB) n

5 6 7 8 9

This information element is set to the security layer packet received from the AT. 7 6 5 4 3 2 1 0 A9 Element Identifier = [89H] Length (MSB) Security Layer Packet

10 11 12 13

Length

This field contains the number of octets in this information element following this field as a binary number.

Security Layer Packet This field is set to the security layer packet received from the AT.

A-47

A.S0007-A v3.0 HRPD IOS

1 2 3

May 2007

6.2.2.200

System Time

This information element is used to validate the security layer packet included in the associated message. 7 6 5 4 3 2 1 0 Octet 1 2 3 4 (LSB) 10

A14 Element Identifier = [8CH] Length = [08H] (MSB) CDMA System Time

4 5 6 7 8 9 10

Length CDMA System Time

This field contains the number of octets in this information element following this field as a binary number. This is the common CDMA system-wide time to which all AN digital transmissions are referenced. Refer to [1].

6.2.2.201

HRPD A9 Indicators 0 Octet 1 2

Default Session Indicator = [0, 1] Session Information Required = [0, 1] 3

This information element provides status between the BS and the PCF. 7 6 5 4 3 2 1 A9 Element Identifier = [8BH] Length = [01H]

Reserved

11 12 13 14 15 16 17 18 19 20

Length Session Information Required Default Session Indicator

This field contains the number of octets in this information element following this field as a binary number. This field is set to `1' to request Session Information Record from the PCF. This field is set to `1' when the message includes default session information that is required to be configured over the air. Otherwise, this field is set to `0'.

6.2.2.202

Session State Information Record Octet

1 2

This information element is used to send HRPD Session Information as specified in [10]. 7 6 5 4 3 2 1 0

A9 Element Identifier = [8AH] (MSB) (MSB) Length = [variable]

(LSB)

Session State Information Record (LSB)

3

4 n

A-48

May 2007

1 2 3 4 5 6

A.S0007-A v3.0 HRPD IOS This field contains the number of octets in this information element following this field as a binary number. This field contains the air interface protocol attributes and associated public data. The format is as specified in [10].

Length Session State Information Record

A-49

May 2007

A.S0007-A v3.0 HRPD IOS

1

Annex B

2.15

A10-A11 (AN/PCF - PDSN) Interface Change Text

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48

A10/A11 Interface Procedures

A10/A11 interface uses Mobile IP messages for managing the A10 connections. The following sections describe the messages and procedures for the A10/A11 interfaces. The sections are as follows: · · · · · A10 Connection Setup Procedures, A10 Connection Re-Registration Procedures, A10 Connection Release Procedures, A10 Connection Accounting Procedures, and A10/A11 Interface Call Flows for 1x and HRPD mobiles.

When originating in a 1x system, The mobile subscriber initiates a packet data call is initiated by sending an IS-2000 Origination Message. Normal voice service authentication procedures are followed for the subscriber, and then a traffic channel is established with the mobile. After connection of a packet data service option, RLP synchronization between the mobile station and the BS proceeds. When originating in an HRPD system, a packet data session is initiated as specified in TIA/EIA/IS-856. Terminal authentication of the AT may be performed via the AN-AAA server. After establishment of a packet data session in the AN and allocation of radio resources, the The BS/PCF initiates setup of an A10 connection with the PDSN by sending an A11-Registration Request message on the A11 interface. The PDSN may accept or reject the connection setup request. If the connection setup request is acceptable, the PDSN returns an A11-Registration Reply message with an accept indication, and the packet data call is connected through the just established A10 connection. With the A10 connection in place, link layer/network layer frames pass over this connection in both directions via Generic Routing Extension Encapsulation (GRE) framing. The PDSN accepts these frames, strips the GRE, and processes them as normal incoming frames for the appropriate interface and protocol. The other direction behaves analogously, with the PDSN encapsulating the link layer/network layer frames in GRE, and the PCF stripping the GRE before passing the frames over to the upper layer. At this point, there is a point-to-point link layer/network layer connection between the MS/AT mobile user and the PDSN. In order to setup an A10 connection, the PCF assigns a PCF Session Identifier (PSI) to the packet data bearer. The Mobile PCF Session Identifier (PSI) is unique only within the PCF entity. The PCF also use the MN Session Reference ID (MN-SRID) which is passed from the mobile on each 1x origination and which, together with the Mobile Identifier, can be used to identify a packet data service session for a specific mobile across PCFs and PDSNs. In the case of HRPD, the MN-SRID is not received from the AT during origination and the AN/PCF shall set this to the default value of 1. Note that not setting the SRID of the packet data service session to one may cause problems for handoffs between HRPD and 1x systems. In the A11-Registration Request message, the PCF sets the Home Address field to zeros. The IP source address (IP header) and the Care-of-Address field of the A11-Registration Request message are set to the IP address of the PCF. The IP destination address in the IP header and the Home Agent field in the A11-Registration Request message are set to the address of the PDSN designated for the call. The PCF Session Identifier (PSI), link layer/network layer Protocol Type identifier, MN Session Reference ID and IMSI address of the mobile subscriber are set in the Session Specific Extension of the A11-Registration Request message. When the A10/A11 interface is used between an HRPD AN/PCF and a PDSN, the MN ID that is used by the AN and the PCF on A8/A9 and A10/A11 messages is determined as follows: · If the HRPD AN uses the terminal authentication feature, the MN ID field shall be set to the MN ID value returned by the AN-AAA (e.g., IMSI) following successful terminal authentication. · Otherwise, the AN/PCF shall set the MN ID field to a value that conforms to a valid MN ID format (e.g., IMSI format). In this case, the MN ID is determined by other means. If the MN_ID is not the IMSI, then handoff between HRPD and 1x systems is not supported. B-1

A.S0007-A v3.0 HRPD IOS

1 2 3 4 5 6 7 8 9 10

May 2007

The A10 bearer connection is used for the transport of user data for a packet data session. Link layer / network layer frames are carried between the PCF and the PDSN encapsulated in GRE packets, which in turn are carried over IP. The PCF-Address and the PDSN-Address are used in the source address and destination address fields of the IP header used with the GRE packet. The key field in the GRE header contains the PCF Session Identifier (PSI), and indicates which packet data bearer connection a particular payload packet belongs to. The A11-Registration Request and A11-Registration Reply messages are defined by RFC 2002 with extension elements defined in section 6.1.11 of this standard. The A11-Registration Update and A11Registration Acknowledge messages are also defined in section 6.1.11 of this standard. The procedures for the use of these messages are defined in section 2.15.1 of this standard. 2.15.1 A10 Interface Setup Procedures No changes from TIA/EIA/IS-2001-A text. 2.15.1.1 A10 Connection Establishment

11 12

13 14

No changes from TIA/EIA/IS-2001-A text. 2.15.1.1.1 Successful Operation

15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

When the 1x BS receives an Assignment Request with a Service Option that requests packet data service from the MSC, it initiates the procedure for establishing radio traffic channels. After traffic channels are established, the BS/PCF initiates procedures for establishing an A10 connection. For the HRPD system, after the AN and the mobile have established an HRPD session, the AN/PCF initiates procedures for establishing an A10 connection. The PCF initiates setup of an A10 connection by sending an A11-Registration Request message to the PDSN and starts timer Tregreq. The A11-Registration Request message is structured as specified in RFC 2002 and contains the extensions specified in this standard. The A11-Registration Request message may be retransmitted a configurable number of times as specified in RFC 2002. If the connection setup request is acceptable, the PDSN updates its binding record for the A10 connection by creating an association between the MN ID IMSI address and the PCF Session Identifier, PCF-Address and PDSN-Address information. It then returns an A11-Registration Reply message with an accept indication, including the configured Lifetime (Trp) for the A10 connection. The packet data call is connected through the just established A10 connection. The PCF and the PDSN use the PCF-IP-Address and the PDSN-IP-Address returned in the A11Registration Reply message as the A10 connection for the transport of user traffic. The PCF-IP-Address and the PDSN-IP-Address form the unique link layer ID for each A10 connection. The PCF and the PDSN maintain an association of the mobile's MN ID IMSI address with the A10 connection. The PCF and the PDSN use the PCF-Address and the PDSN-Address returned in the A11-Registration Reply message as the A10 connection for the transport of user traffic. The PSI, PCF-Address and the PDSN-Address form the unique link layer ID for each A10 connection. The PCF and the PDSN maintain an association of the mobile's IMSI address with link layer ID over the A10 connection. In the case of Dormant Handoff, the PCF shall initiate the setup of an A10 connection and include a Mobility Event Indicator as CVSE and the PANID and CANID as an NVSE in the A11-Registration Request message. Please refer to RFC 2002 and section 6.1.11.1 "A11-Registration Request" for the format and content of the A11-Registration Request message. 2.15.1.1.2 Failure Operation

43

B-2

May 2007

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

A.S0007-A v3.0 HRPD IOS

The PCF initiates setup of an A10 connection by sending an A11-Registration Request message to a selected PDSN. If the selected PDSN does not accept the connection, it returns an A11-Registration Reply message with a reject result code. The PDSN may return an A11-Registration Reply message with result code `88H' (Registration Denied unknown PDSN address). When code `88H' is used, an alternate PDSN address is included in the A11Registration Reply message. The address of the alternate proposed PDSN shall be returned in the Home Agent field of the A11-Registration Reply message. On receipt of an A11-Registration Reply message with code `88H', the PCF shall either initiate establishment of the A10 connection with the proposed PDSN by sending a new A11-Registration Request message as indicated in this section, or shall use internal algorithms to select a new PDSN. On receipt of an A11-Registration Reply message with another result code, depending on the result code, the PCF may attempt to re-try setting up the A10 connection. If the A10 connection can not be established, the PCF indicates this to the AN which releases the call or to the BSC, which returns a failure indication to the MSC, which in-turn releases the call. Reliable message delivery mechanisms are used for setting up the A10 connection between the PCF and the PDSN. As specified in RFC 2002, the A11-Registration Request message may be retransmitted if no A11-Registration Reply message is received within a configurable time. A call is considered to have failed if no A11-Registration Reply message is received after a configurable number of A11-Registration Request retransmissions. 2.15.2 A10 Interface Operational Procedures No changes from TIA/EIA/IS-2001-A text. 2.15.2.1 A10 Connection ­ Periodic Re-registration

20 21

22 23

No changes from TIA/EIA/IS-2001-A text. 2.15.2.1.1 Successful Operation

24 25

No changes from TIA/EIA/IS-2001-A text. 2.15.2.1.2 Failure Operation

26 27

No changes from TIA/EIA/IS-2001-A text. 2.15.3 A10 Interface Release Procedures The release of an A10 connection is controlled by the PCF. For PDSN initiated A10 connection release, the PDSN requests that the PCF release the connection. The BSC or AN then would releases the traffic channel(s) accordingly. 2.15.3.1 A10 Connection Release ­ PCF Requested

28 29 30 31

32 33

No changes from TIA/EIA/IS-2001-A text. 2.15.3.1.1 Successful Operation

34 35

No changes from TIA/EIA/IS-2001-A text. 2.15.3.1.2 Failure Operation

36 37

No changes from TIA/EIA/IS-2001-A text. 2.15.3.2 A10 Connection Release ­ PDSN Initiated

38 39 40

The PDSN may initiate release of an A10 connection by sending an A11-Registration Update message to the PCF. B-3

A.S0007-A v3.0 HRPD IOS

1 2 3 4

May 2007

In the case of a PDSN initiated release of the A10 connection, the PCF indicates this to the AN which releases the traffic resources accordingly or to the BSC, in this release, which returns an indication to the MSC. Please refer to section 6.1.11.3, "A11-Registration Update", for the format and content of this message. 2.15.3.2.1 Successful Operation

5 6

No changes from TIA/EIA/IS-2001-A text. 2.15.3.2.2 Failure Operation

7 8 9 10 11 12 13 14 15 16 17 18

On failure to receive an A11-Registration Acknowledge or an A11-Registration Request message (with accounting related information and Lifetime set to zero) in response to a configurable number of A11Registration Update retransmissions or on receiving an A11-Registration Acknowledge with an update denied status, the PDSN removes the binding information for the A10 connection. When PCF returns Registration denied, the PDSN may send a new registration update at a configurable number of time. On the release of the A10 connection, the PCF indicates this to the AN which releases the resources associated with the connection or to the BSC, which returns an indication to the MSC (if required), which in-turn initiates release of the call. Please refer to section 6.1.11.4, "A11-Registration Acknowledge", for the format and content of this message. 2.15.4 A10 Interface Packet Accounting Procedures The PCF uses the A11-Registration Request message to send accounting related and other information to the PDSN. The accounting related information is accumulated at the PCF and sent to the PDSN on occurrence of pre-defined triggers, which are listed in Table 2.15.4-1 below. The occurrence of these predefined triggers is fully specified in TIA/EIA/IS-835. The A10 connection binding information at the PDSN and the PCF may also be updated appropriately depending on the setting of the Lifetime field. Table 2.15.4-1 - Accounting Records Generated By The PCF Airlink Record Type (Y1) Accounting Records Generated By The PCF Y1=1 Y1=2 Y1=3 Y1=4

4

19 20 21 22 23 24 25

Connection Setup: Setup of A10 connection initiated Active Start: Mobile comes on the traffic channel(s). Active Stop: Mobile has stopped use of traffic channel(s). A forward or reverse short data burst (SDB) was exchanged with the mobile

26 27 28 29 30 31 32 33 34

If some airlink parameters for an active session change, the PCF generates an "Active Stop (Y1=3)" accounting record followed by an "Active Start (Y1=2)" accounting record. For successful operation, the PDSN saves the accounting related and other information for further processing, and responds with A11Registration Reply message with an accept indication. See section 6.2.2.166 Vendor/Organization Specific Extension for detailed information on all the airlink record types and the accounting parameters required for each airlink record type. If the accounting parameter specified for an airlink record type is not received at the PDSN, the PDSN shall return an A11Registration Reply message with result code `8DH' (Registration Denied - unsupported Vendor ID or unable to interpret data in the CVSE'.

4

Y1=4 Airlink record is only applicable to 1x systems.

B-4

May 2007

1 2 3 4

A.S0007-A v3.0 HRPD IOS

The following is a description of the accounting events and indicates which airlink record type shall be used for each event. If a specified airlink record type is not received at the PDSN or on receipt of an unspecified airlink record type, the PDSN shall return an A11-Registration Reply message with result code `8DH' (Registration Denied ­ unsupported Vendor ID or unable to interpret data in the CVSE'. 2.15.4.1 A10 Connection Setup Airlink Record

5 6

No changes from TIA/EIA/IS-2001-A text. 2.15.4.2 Active-Start Airlink Record

7 8 9 10 11 12 13 14 15 16 17 18

An Active-Start Airlink record shall be included in the A11 Registration Request to the PDSN for any of the following event: 1. For a 1x system wWhen a traffic channel is assigned to a packet data session: during initial call setup, on transition from dormant to active state or during handoff or for an HRPD IOS system when the air interface is in an appropriate state such that bearer data is ready to be exchanged. The Active-Start Airlink record may follow the connection Setup Airlink record in the same A11- Registration Request message (assuming that all the parameters required in the Active-Start Airlink record are made available at the PCF at that time. 2. Following an Active-Stop Airlink record (for 1x systems), when any of the parameters (QoS, User Zone, Forward/Reverse Mux Option') currently defined in Active Start are changed. The Active Start will contain the new set of parameters. 2.15.4.3 Active-Stop Airlink Record

19 20

No changes from TIA/EIA/IS-2001-A text. 2.15.4.4 SDB Airlink Record

21 22

No changes from TIA/EIA/IS-2001-A text. 2.15.4.5 Accounting at Re-registration

23 24

No changes from TIA/EIA/IS-2001-A text. 2.15.4.6 Sequence Numbers

25 26

No changes from TIA/EIA/IS-2001-A text. 2.15.4.7 Accounting update due to parameter changes

27 28

No changes from TIA/EIA/IS-2001-A text.

29

30 31

6.1.11

A11 Interface Message Formats

No changes from TIA/EIA/IS-2001-A text. 6.1.11.1 A11-Registration Request

32 33

No changes from TIA/EIA/IS-2001-A text. 6.1.11.2 A11-Registration Reply

34

35 36

This A11 interface message is sent from the PDSN to the PCF in response to an A11-Registration Request message.

B-5

A.S0007-A v3.0 HRPD IOS

Information Element A11 Message Type Code Lifetime Home Address Home Agent Identification Session Specific Extension Critical Vendor/Organization Specific Extension Mobile-Home Authentication Extension

1 2 3

May 2007

Section Reference 6.2.2.154 6.2.2.161 6.2.2.156 6.2.2.157 6.2.2.158 6.2.2.160 6.2.2.165 6.2.2.166 6.2.2.163 Element Direction PDSN -> PCF PDSN -> PCF PDSN -> PCF PDSN -> PCF PDSN -> PCF PDSN -> PCF PDSN -> PCF PDSN -> PCF PDSN -> PCF M M M M Ma M M Ob O C R Type

a. This element can also be used to identify the IPv4 address of an alternative PDSN. b. One or more instances of this element may be included in the A11-Registration Reply message. The following table shows the bitmap layout for the A11-Registration Reply message

0 1 2 3 4 5 6 7 Octet 1 1 A11 Message Type = [03H] Code = [ 00H (Registration Accepted), 80H (Registration Denied ­ reason unspecified) 81H (Registration Denied -- administratively prohibited) 82H (Registration Denied ­ insufficient resources) 83H (Registration Denied ­ mobile node failed authentication) 85H (Registration Denied ­ identification mismatch) 86H (Registration Denied ­ poorly formed request) 88H (Registration Denied ­ unknown PDSN address) 89H (Registration Denied ­ requested reverse tunnel unavailable) 8AH (Registration Denied ­ reverse tunnel is mandatory and `T' bit not set) 8DH (Registration Denied ­ unsupported vendor ID or unable to interpret data in the CVSE) 8EH (Registration Denied ­ nonexistent A10 or IP flow)] (MSB) Lifetime = [00 00 H to FF FF H] (LSB) (MSB) Home Address = [00 00 00 00 H] (LSB) -- Continued on next page -1 2 1 2 3 4

4

B-6

May 2007

1

A.S0007-A v3.0 HRPD IOS

-- Continued from previous page -(MSB) Home Agent = <any value> (LSB) (MSB) 1 2 3 4 1 2 3 Identification = <any value> 4 5 6 7 (LSB) Session Specific Extension: Type = [27H] Length = [13H ­ 15H] (MSB) (MSB) Key (PCF Session Identifier) = <any value> (LSB) Reserved = [00 00 H] (MSB) (MSB) MN Session Reference Id = <any value> (LSB) MN ID Type = [00 06 H] (IMSI) (LSB) MN ID Length = [06-08H] (10-15 digits) Identity Digit 1 = [0H, 9H] (BCD) Identity Digit 3 = [0H, 9H] (BCD) ... If (Odd/Even Indicator = 0000 (even)) {Identity Digit N+1 = [FH] (BCD)} Else If (Odd/Even Indicator = 0001 (odd)) {Identity Digit N+1 = [0H, 9H] (BCD)} Odd/Even Indicator = [0000, 0001] Identity Digit 2 = [0H, 9H] (BCD) ... Identity Digit N = [0H, 9H] (BCD) Protocol Type = [ 88 0BH, 88 81H ] (LSB) 8 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 ... 21-23

-- Continued on next page -2

B-7

A.S0007-A v3.0 HRPD IOS

1

May 2007

-- Continued from previous page --

Critical Vendor/Organization Specific Extension: Type = [ 26H]

Reserved = [0000 0000] (MSB) Length = 00 06H (MSB) 3GPP2 Vendor ID = 00 00 15 9FH (LSB) Application Type = [03H] IF (Application Type = 01H (Accounting) {1: Application Sub Type = [01 H] (MSB) Application Data (contains accounting information) (LSB)

1 2

3 4 5

6

7 8

9

10 11

...

(LSB) Application Sub Type = [01H] } Application Type = 02H Mobile-Home Authentication Extension: Type = [20H] Length = [ 14H ] (MSB) SPI = [00 00 01 00H to FF FF FF FF H] (LSB) (MSB) Authenticator = <any value > (keyed-MD-5 authentication) ... (LSB)

2

k m 1 2 3 4 5 6 7 8 9 ... 22

} Application Type = 01H; ELSE IF (Application Type = 02H (Mobility Event Indicator)) {1:

3 4

6.1.11.3

A11-Registration Update

No changes from TIA/EIA/IS-2001-A text. 6.1.11.4 A11-Registration Acknowledge

5 6

No changes from TIA/EIA/IS-2001-A text.

7

8 9

6.2.2.154

A11 Message Type

No changes from TIA/EIA/IS-2001-A text. B-8

May 2007

1 2

A.S0007-A v3.0 HRPD IOS Flags

6.2.2.155

No changes from TIA/EIA/IS-2001-A text. 6.2.2.156 Lifetime

3 4

No changes from TIA/EIA/IS-2001-A text. 6.2.2.157 Home Address

5 6

No changes from TIA/EIA/IS-2001-A text. 6.2.2.158 Home Agent

7 8

No changes from TIA/EIA/IS-2001-A text. 6.2.2.159 Care-of-Address

9 10

No changes from TIA/EIA/IS-2001-A text. 6.2.2.160 Identification

11 12

No changes from TIA/EIA/IS-2001-A text. 6.2.2.161 Code

13 14 15

This element identifies the result of processing an A11-Registration Request message. The structure of the element conforms to RFC 2002 and is shown below. 0 1 2 3 Code 4 5 6 7 Octet 1

16

The supported Code values are listed in Table 6.2.2.161-1. Table 6.2.2.161-1 - A11 Code Values

Hex Value 00H 80H 81H 82H 83H 85H 86H 88H 89H 8AH 8DH 8EH Decimal Value 0 128 129 130 131 133 134 136 137 138 141 142 Code Registration Accepted Registration Denied ­ reason unspecified Registration Denied ­ administratively prohibited Registration Denied ­ insufficient resources Registration Denied ­ mobile node failed authentication Registration Denied ­ identification mismatch Registration Denied ­ poorly formed request Registration Denied ­ unknown PDSN address Registration Denied ­ requested reverse tunnel unavailable Registration Denied ­ reverse tunnel is mandatory and `T' bit not set Registration Denied ­ unsupported Vendor ID or unable to interpret data in the CVSE Registration Denied ­ nonexistent A10 or IP flow All other values reserved

17

18 19

6.2.2.162

Status

No changes from TIA/EIA/IS-2001-A text. 6.2.2.163 Mobile-Home Authentication Extension

20 21

No changes from TIA/EIA/IS-2001-A text. B-9

A.S0007-A v3.0 HRPD IOS

1 2

May 2007

6.2.2.164

Registration Update Authentication Extension

No changes from TIA/EIA/IS-2001-A text. 6.2.2.165 Session Specific Extension

3 4

No changes from TIA/EIA/IS-2001-A text. 6.2.2.166 Critical Vendor/Organization Specific Extension

5 6 7 8 9 10 11 12 13 14 15 16

This element may be present in the A11-Registration Request message to convey the accounting information from the PCF to the PDSN. This element may also be present in the A11-Registration Request message to convey the Mobility Event Indicator from the PCF to the PDSN during dormant handoffs and active/hard handoffs. For alternative coding formats see RFC 2138. This element may be present in the A11-Registration Reply message to convey the Data Available Indicator (DAI) from the PDSN to the PCF during handoff. When used to convey the accounting information, the accounting records are contained within the Application Data field of this element. The accounting records conveyed from the PCF to the PDSN conform to the specifications in TIA/EIA/IS-835 (Wireless IP Network Standard). Each application type 01H (Accounting) VSE contains one and only one airlink record. For transmission of multiple airlink records in the same A11-Registration Request message, multiple instances of accounting type VSEs are used.

0 1 2 3 4 5 6 7 Octet 1 2 3 (LSB) 4 5 3GPP2 Vendor ID (LSB) Application Type Application Sub Type (MSB) Application Data (LSB) 6 7 8 9 10 11 12 ... ... k

A11 Element Identifier (Type) Reserved (MSB) Length (MSB)

17 18 19 20 21 22 23

Type: Length: 3GPP2 Vendor ID: Application Type:

26H This field indicates the number of octets in this element following this field. 00 00 15 9FH This field indicates the type of the application, that the extension relates to. The supported values are:

B-10

May 2007

1

A.S0007-A v3.0 HRPD IOS Table 6.2.2.166-1 - Vendor/Organization Specific Extension - Application Type

Hex Value 01H 02H 03H Description Accounting Mobility Event Indicator Data Available Indicator All other values reserved.

2 3 4 5 6

Application Sub Type: This one octet field indicates the Application sub-type within the Application Type. The supported values are listed in Table 6.2.2.166-2.

Table 6.2.2.166-2 - Application Sub Type

Application Type Application Type Name Accounting HEX Value 01 H Application Sub Type Application Sub Type Name RADIUS DIAMETER Mobility Event Indicator 02H Mobility HEX Value 01H 02H 01H

All other values are reserved

All other values are reserved

Data Available Indicator

03H

Data Ready to Send

01H

All other values are reserved All other values are reserved

7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

Application Data:

For Application Type 01H (Accounting), this field contains the accounting parameters conveyed from the PCF to the PDSN as specified in TIA/EIA/IS-835 (Wireless IP Network Standard). Each of the accounting parameters are structured in the format of RADIUS attributes specified in RFC 2138 and RFC 2139. This field is used in messages sent from the PCF to the PDSN. For Application Type 02H (Mobility Event Indicator), this field is zero bytes in length. This field is used in messages sent from the PCF to the PDSN. For Application Type 03H (Data Available Indicator), this field is zero bytes in length. This field is used in messages sent from the PDSN to the PCF.

For Application Type 01 H (Accounting) all 3GPP2 specific Airlink Record Parameters are coded as follows:

B-11

A.S0007-A v3.0 HRPD IOS

1

May 2007

1

2

3

4 Type Length

5

6

7

8

Octet 1 2 3 4

(MSB) 3GPP2 Vendor-Id (LSB) Vendor-Type Vendor-Length MSB

5 6 7 8 9 10

Vendor-Value (variable number of octets) (LSB)

2 3 4 5 6 7 8 9 10 11 12 13 14

... k

Type: Length:

1A H Type (1 octet ) + Length (1 octet ) + 3GPP2 Vendor Id (4 octets) + { Vendor-Type (1 octet), Vendor-Length (1 octet), Vendor-Value (variable octets) of the 3GPP2 specific parameter comprising the airlink record being coded.} 00 00 15 9F H Sub-Type value from the Airlink Record table below. Vendor-Type (1 octet) + Vendor-Length (1 octet) + Payload Length (in octets) from the Airlink Record table below.

Vendor ID: Vendor Type: Vendor-Length:

For Application Type 01 H (Accounting) all RADIUS specific Airlink Record Parameters are coded as follows:

1 2 3 4 Type Length MSB 5 6 7 8 Octet 1 2 3 4 Value (variable number of octets) (LSB) ... k

15 16 17

Length:

Type (1 octet) + Length (1 octet) + Payload Length (in octets) from the Airlink Record table below.

B-12

May 2007

1 2

A.S0007-A v3.0 HRPD IOS

Airlink Record Fields Tables: 1. R-P Session Setup Airlink Record (Connection Setup).

Parameter Airlink Record Type = 1 (Setup) R-P Session ID Airlink Sequence number MSID Serving PCF BSID ESN Type 26 26 26 31 26 26 26 SubType 40 41 42 N/A 9 10 48 Max. Payload Length (octet) 4 4 4 15 4 12 4 Format Integer Integer Integer String ip-addr String 5 Integer

3

2. Active Start Airlink Record.

Parameter Airlink record type = 2 (START) R-P Session ID Airlink Sequence number User Zone

6,7 6,7

Type 26 26 26 26 26 26 26

6,7 6,7

SubType 40 41 42 11 12 13 16 17 18 19 20 21 39

Max. Payload Length (octet) 4 4 4 4 4 4 4 4 4 4 4 4 4

Format Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer

Forward Mux Option Reverse Mux Option Service Option

Forward Traffic Type Reverse Traffic Type

26 26 26 26 26

7 6,7

6,7 6,7

Fundamental Frame Size

Forward Fundamental RC Reverse Fundamental RC

6,7

Airlink Quality of Service (QoS)

4

26

3. Active Stop Airlink Record.

Parameter Airlink record type = 3 (STOP) R-P Session ID Airlink Sequence number Active Connection Time in Seconds Type 26 26 26 26 SubType 40 41 42 49 Max. Payload Length (octet) 4 4 4 4 Format Integer Integer Integer Integer

5

5 A number formed from the concatenation of SID+NID+ Cell Identifier (Type 2), where each item is encoded using four

hexadecimal upper case ASCII characters. 6 7 This parameter need not be included in HRPD systems. If it is included, the PCF shall set this field to a default value of 0. If the PCF has not received this information from the AN, the PCF shall set this field to a default value of 0.

B-13

A.S0007-A v3.0 HRPD IOS

1

May 2007

4. SDB Airlink Record.

Parameter Airlink record type = 4 (SDB) R-P Session ID Airlink Sequence number Mobile Orig./Term. Indicator SDB Octet Count Type 26 26 26 26 26 SubType 40 41 42 45 31/32

8

Max. Payload Length (octet) 4 4 4 4 4

Format Integer Integer Integer Integer Integer

2 3 4

An example coding of the Active Stop Airlink Record within the Vendor/Organization Specific Extension element is illustrated below:

0 1 2 3 4 5 6 7 Octet 1 2 3 (LSB) 4 5 3GPP2 Vendor ID = 00 00 15 9F H (LSB) Application Type = 01 H Application Sub Type = 01 H Parameter Name: Airlink Record Type = 3 (Active Stop) Type = 1A H Length = 0C H (MSB) 3GPP2 Vendor-Id = 00 00 15 9F H (LSB) Vendor-Type = 28 H Vendor-Length = 06 H MSB 11 12 13 14 15 16 17 18 19 20 Vendor-Value = 3 (Active Stop) (LSB) Continued on next page 21 22 6 7 8 9 10

A11 Element Identifier = 26H Reserved (MSB) Length = 30 H (MSB)

8 Subtype 31 is for terminating SDB octet count, subtype 32 is for originating SDB octet count. B-14

May 2007

1

A.S0007-A v3.0 HRPD IOS

Continued from previous page Parameter Name: R-P-Session ID Type = 1A H Length = 0C H (MSB) 3GPP2 Vendor-Id = 00 00 15 9F H (LSB) Vendor-Type = 29 H Vendor-Length = 06 H (MSB) 23 24 25 26 27 28 29 30 31 32 Vendor-Value = PCF Session Identifier (LSB) Parameter Name: Airlink Sequence Number Type = 1A H Length = 0C H (MSB) 3GPP2 Vendor-Id = 00 00 15 9F H (LSB) Vendor-Type = 2A H Vendor-Length = 06 H (MSB) 35 36 37 38 39 40 41 42 43 44 Vendor-Value = Sequence Number (LSB) Parameter Name: Active Connection Time Type = 3A H Length = 06 H (MSB) 47 48 49 50 Value = Active Connection Time (in seconds) (LSB)

2

33 34

45 46

51 52

B-15

A.S0007-A v3.0 HRPD IOS

1 2

May 2007 No text.

B-16

May 2007

A.S0007-A v3.0 HRPD IOS

1

Annex C

A12 RADIUS Attributes

2 3

This is the general Vendor Specific Format for all 3GPP2 RADIUS attributes. The type and vendor ID are the same for every attribute. The vendor type, vendor length, and value are specified as follows.

1 2 3 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Vendor-Id +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Vendor-Id (cont) | Vendor-type |Vendor-length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vendor-value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type = cdma specific Length >= 9

4 5

Figure C-1 Type: Length: 26 (1AH)

3GPP2 RADIUS Attribute Format

6 7 8 9 10 11 12 13 14 15

greater than 9 (> 09H)

3GPP2 Vendor ID: 5535 (0000159FH) HRPD Terminal Authentication: Indicates whether the Access Request is in the context of terminal authentication. This optionally appears in an Access-Request message, on the A12 interface. Vendor-Type = 60 (3CH) Vendor-Length = 6 (06H) Vendor-Value = 1 (00000001H) for HRPD Terminal Authentication

C-1

A.S0007-A v3.0 HRPD IOS

1 2

May 2007 No text.

C-2

May 2007

A.S0007-A v3.0 HRPD IOS

1

Annex D

Revision History

May 12, 2003 May 2007 TIA-1878 publication A.S0007-A v3.0 publication

2

3 4

D-1

1 2

No text.

D-2

Information

A.S0007-A v3.0 HRPD IOS pub.doc

222 pages

Find more like this

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

686036


You might also be interested in

BETA
Microsoft Word - USDOT NG911 Task 4A3 - Transition Plan Final 020209.doc
A.S0007-A v3.0 HRPD IOS pub.doc
Microsoft Word - 2CSPCM6224X_6248X-RN102-R.doc
Microsoft Word - 13National Online Examination System An Architectural Perspective.doc