1xEV-DO Inter-Operability Specification (IOS) for CDMA 2000 Access Network Interfaces

Transcription

1 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version GPP A.S000 Ballot Version Date: June, 00 xev-do Inter-Operability Specification (IOS) for CDMA 000 Access Network Interfaces Release 0 (Ballot Version) COPYRIGHT 00, GPP GPP 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 GPP Secretariat at secretariat@gpp.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See for more information.

2

3 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version xev-do Inter-Operability Specification (IOS) for CDMA 000 Access Network Interfaces SP--000 Ballot Version: June, 00

4

5 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version Table of Contents Foreword...v Introduction Scope xev-do IOS Architecture Reference Model References Terminology Acronyms Definitions Document Convention Compatibility with IS-00 Standards xev-do IOS Assumptions... - xev-do IOS Call Flows AT Originates xev-do Session AT Originates xev-do Session -Successful Authentication AT Originates xev-do Session - Unsuccessful Authentication AT Originates with a Pre-existing xev-do Session Data Delivery Data Delivery - AT Terminated Data Delivery - AT Originated Connection Tear-Down Connection Tear-Down on xev-do Network - Initiated by the AT Connection Tear-Down on xev-do Network - Initiated by the AN/PCF Session Tear-Down Session Tear-Down - Initiated by the AT A0 Tear-Down - Initiated by the PDSN Radio Session Tear-Down - Initiated by the AN Dormant Handoff of xev-do AT between ANs - Served by the Same PDSN AN-AN Dormant Handoff with Successful Retrieval of Session Information Dormant AN-AN Handoff with Session Information Transfer Failure... - xev-do and IS-000 IOS Transition Call Flows Dormant/Idle (Voice or Packet) Cross System Handoff - Served by the Same PDSN Dormant/Idle IS-000 Handoff to Idle xev-do - Existing Session Dormant/Idle IS-000 Handoff to Idle xev-do - New Session Idle xev-do Handoff to Dormant/Idle IS AT Terminated Voice Call During Active xev-do Data Session... - i

6 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, AT Terminated Voice Call During Active xev-do Data Session (Intra-PDSN/Inter-PCF) MS/AT Terminated Voice Call During Active xev-do Data Session (Intra-PCF) AN Change, Active IS-000 (Packet) to Active xev-do (Cross System - DO) Status Management Supported by Feature Invocation... - xev-do IOS Interfaces A-A (AN - PCF) Interface A0-A (PCF - PDSN) Interface A (AN - AN AAA) Interface PPP Session Establishment Termination Authentication RADIUS Support Radius Server Requirements A (AN - AN) Interface A Interface Network/Transport Protocol Specification A Interface Procedures A-Session Information Request Successful Operation Failure Operation A-Session Information Response Successful Operation Failure Operation A-Session Information Confirm Successful Operation Failure Operation A-Session Information Reject Successful Operation Failure Operation A Message Definitions A-Session Information Request Message A-Session Information Confirm Message A-Session Information Reject Message A-Session Information Response Message A Information Element Definitions Information Element Identifiers A Message Type... - ii

7 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version 0... Unicast Access Terminal Identifier (UATI) Security Layer Packet SectorID Cause Mobile Identity (MN ID) PDSN IP Address Access Network Identifiers AN State Information Record... - xev-do IOS Timer Definitions Timer T airdrop... - Annex A Informative xev-do IOS Phase + Annex... A- A. xev-do IOS Phase + Architecture Reference Model... A- Annex B A-A (AN - PCF) Interface Change Text...B- Annex C A0-A (AN/PCF - PDSN) Interface Change Text...C- Annex D A RADIUS Attributes... D- Annex E Revision History...E- iii

8 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, Table of Figures Figure.- xev-do IOS Phase Architecture Reference Model... - Figure..- Initial AT Origination (with Session Establishment and Key Exchange)... - Figure..- Initial AT Origination (with Session Establishment and Key Exchange)... - Figure..- AT Origination (Session is Already Established)... - Figure..- AT Terminated Data Delivery... - Figure..- AT Initiated Connection Tear-Down... - Figure..- AN/PCF Initiated Connection Tear-Down... - Figure..- AT Initiated Session Tear-Down... - Figure..- PDSN Initiated A0 Tear-Down Figure..- AN Initiated Radio Session Tear-Down... - Figure..- Inter-PCF/Intra-PDSN Dormant AN-AN HO - Successful Operation... - Figure..- Inter-PCF/Intra PDSN Dormant AN-AN HO - Session Info Transfer Failure... - Figure..- MS/AT Idle Handoff from IS-000 to xev-do - Existing Session... - Figure..- MS/AT Idle Handoff from IS-000 to xev-do - New Session... - Figure..- MS/AT Idle Handoff from a xev-do to an IS-000 System... - Figure..- Voice Call Termination During Active xev-do Data Session (Inter-PCF)... - Figure..- Voice Call Termination During Active xev-do Data Session (Intra-PCF)... - Figure.- MS/AT Active AN Change from an IS-000 to a xev-do System... - Figure.- Terminal Based Status Management (Using Feature Invocation)... - Figure.- RADIUS Protocol Reference Model... - Figure A.- xev-do IOS Phase + Architecture Reference Model... A- Figure D- GPP RADIUS Attribute Format... D- iv

9 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version 0 Foreword This xev-do Inter-Operability Specification (IOS) document is based on TIA/EIA/IS-00-A, the Inter-Operability Specification (IOS) for CDMA 000 Access Network Interfaces. This document describes the protocol and some generic procedures to support the following xev-do 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 xev-do IOS feature, it shall be supported as defined in this standard. Features: Authentication Data delivery Session handoff between ANs. v

10 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00 No text. vi

11 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version Introduction 0. Scope This specification provides the xev-do text and call flows for the following scenarios: N AT originates a xev-do session (including authentication) N xev-do data delivery (both AT terminated and AT originated) N xev-do session tear-down on N Idle handoff of xev-do AT between ANs N Dormant/Idle (voice or packet) IS-000 handoff to/from Idle xev-do (cross system) N Active IS-000 call (packet), AN change to active call on xev-do system (cross system, data only) This may happen via a dormant handoff N AT terminated voice call during active xev-do data session N Status Management and definitions for the following xev-do IOS interfaces: Interface Description A-A (AN - PCF) Interface TIA/EIA/IS-00-A delta text (Annex B) A0-A (PCF - PDSN) Interface TIA/EIA/IS-00-A delta text (Annex B) A (AN - AN AAA) Interface New xev-do IOS defined text (Section.) A (AN - AN) Interface New xev-do IOS defined text (Section.). xev-do IOS Architecture Reference Model The xev-do IOS messaging and call flows are based on the Architecture Reference Model shown in Figure.-, xev-do IOS Phase. The xev-do IOS Phase + Architecture Reference Model is addressed in Annex A. Source Access Network (AN) A A PCF A0 A PDSN Access Terminal (AT) Air Interface A A AN AAA Target Access Network (AN) 0 Figure.- xev-do IOS Phase Architecture Reference Model -

12 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, References RFC, MD Message-Digest Algorithm, April. RFC, The PPP Internet Protocol Control Protocol (IPCP), May,. RFC, Point-to-Point Protocol, July. RFC, PPP in HDLC-Like Framing, July,. RFC 0, Randomness Recommendations for Security, December,. RFC, PPP Challenge Handshake Authentication Protocol (CHAP), August,. RFC, The Network Access Identifier, January,. RFC, Generic Routing Encapsulation (GRE), March, 000. RFC, Remote Authentication Dial In User Service (RADIUS), June, 000. RFC, RADIUS Accounting, June, 000. TIA/EIA/IS-, cdma000 High Rate Packet Data Air Interface Specification, February, 00. TIA/EIA/IS-00, Inter-Operability Specification (IOS) for CDMA 000 Access Network Interfaces, December, 000. TIA/EIA/IS-00-A, Inter-Operability Specification (IOS) for CDMA 000 Access Network Interfaces, May, 00.. Terminology 0.. Acronyms xev-do AAA AN AT BS BSC CANID CHAP IMSI IOS IPCP LCP MAC MEI MN ID MS MSC NAI x Evolution - Data Only Authentication, Authorization and Accounting Access Network Access Terminal Base Station Base Station Controller Current Access Network Identifiers Challenge Handshake Authentication Protocol International Mobile Subscriber Identity Inter-Operability Specification Internet Protocol Control Protocol Link Control Protocol Medium Access Control Mobility Event Indicator Mobile Node Identification Mobile Station Mobile Switching Center Network Access Identifier -

13 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version NID PANID PCF PDSN PPP PZID RADIUS SID SKey UATI 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 System Identification Session Key Unicast Access Terminal Identifier Definitions Access Stream The IS- stream whose end-points are the Access Terminal and the Access Network (radio network). This stream is used for access authentication. Access Network Access Terminal AN AAA Connection Hybrid MS/AT Mobile Station Service Stream Session 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 an IS-000 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 an IS-000 systems. An entity that performs authentication and authorization functions for the Access Network. A 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 session the access terminal and the access network can open and can close a connection multiple times. A device capable of operating on both IS-000 and xev-do access networks. An entity in the (IS-000) public cellular radio telecommunications service intended to be used while in motion or during halts at unspecified points. Mobile stations include portable units (e.g., hand-held personal units) and units installed in vehicles. The IS- stream whose end-points are the Access Terminal and the PDSN. This stream is used for packet data exchange. A session refers to a shared state between the access terminal and the access network. This shared state stores the protocols and protocol configurations that were negotiated and are used for communications between the access terminal and the access network. Other than to open a session, an access terminal cannot communicate with an access network without having an open session. The xev-do session and the A0/A connection are not associated with each other. The A0/ A connection may not be established even if the xev-do session is established. The xev-do session may not be released even if the A0/A connection is released. -

14 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00. 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 Compatibility with IS-00 Standards The xev-do IOS interface, as defined in this specification, is compatible with a TIA/EIA/IS-00 or higher release, with the provision that the xev-do capabilities are the same as those supported by the interoperability specification, for the access network(s) in use. For example, when inter-operating with a TIA/EIA/IS-00 system, the portions of this specification related to concurrent services and support for Previous/Current Access Node Identifies (PANID/CANID) are not applicable. Note: When the procedures between TIA/EIA/IS--B / IS-000 and xev-do systems differ, the xev-do procedures are identified separately within this specification. When the TIA/EIA/IS-00 text is applied to the xev-do RAN specification, the procedures related to the MSC shall be ignored. Hard Handoff procedures are not applicable to xev-do. When interpreting TIA/EIA/IS-00 in the context of TIA/EIA/IS-, the following TIA/EIA/IS-00 terms should be mapped as follows. TIA/EIA/IS-00 term BS Base Station BSC Base Station Controller Call MS Mobile Station TIA/EIA/IS- term AN Access Network AN Access Network Connection AT Access Terminal 0. xev-do IOS Assumptions The following assumptions are made regarding AN/AT behavior: N N N A unique value (TBD) is used in the Service Option fields in accounting records transported on the A and A interfaces to identify accounting records associated with xev-do Packet Data Service. For the case of idle inter-an inter-pcf handoff, the target PCF may use the PDSN address received from the source AN to send the A-Registration Request. Otherwise, the target PCF shall use the PDSN selection algorithm (if supported) or internal algorithms to select a PDSN. For the case of idle inter-an handoff, the target AN shall use the PANID received from the AT. If the AT does not send the PANID or the AN chooses not to request this information from the AT, then the target AN may use the PANID received from the source AN. -

15 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version 0 0 N N N N N N Note: Since the AT may have visited an IS-000 system and established a data session between the time it made an idle handoff from the source AN to target AN, the target AN shall use the PANID given to it by the AT (if any) over the PANID received in the A-Session Information Accept message from the source AN. For the instance of Packet Application terminated in the AN, the AT shall support CHAP authentication. In this case, the AT shall send a Network Access Identifier (NAI) of the form specified in RFC. For the instance of Packet Application terminated in the AN (i.e. AN 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. If the AT device authentication feature is used, the AN shall always propose CHAP as a PPP option in an initial Link Control Protocol (LCP) Configure-Request during the PPP establishment. The MN ID that is used by the AN and the PCF on A/A and A0/A messages is determined as follows: S If the xev-do AN uses the AT device authentication feature, the MN ID field shall be set to the MN ID value returned by the AN-AAA (e.g., IMSI) following successful access authentication. S 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. After the AT indicates it is ready to exchange data on the access stream, the AT and the AN initiate PPP procedures according to RFC. The AT may support Mobile IP. -

16 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00 No text. -

17 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version xev-do IOS Call Flows This section describes the call flows associated with a xev-do Access Terminal (AT).. AT Originates xev-do Session This section describes the call flows associated with an AT call origination in the Access Network (AN)... AT Originates xev-do Session -Successful Authentication This section describes the call flow for a successfully authenticated AT call origination in the AN. AT AN AN AAA PCF PDSN time UATI-Request UATI-Assignment a b UATI-Complete c Session Establishment d AT Ready to Exchange Data on Access Stream e PPP and LCP Negotiation f CHAP Challenge - Response g A Access-Request A Access-Accept h i CHAP - Authentication Success j AT Ready to Exchange Data on Packet Data Stream k A-Setup-A l A-Registration Request (Lifetime, MEI) m T A-setup T regreq A-Registration Reply (Lifetime, accept) n A-Connect-A o Establishing PPP connection p Transmitting Packet Data q Figure..- Initial AT Origination (with Session Establishment and Key Exchange) -

18 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, a. The AT sends a UATI-Request message to request that a Unicast Access Terminal Identifier (UATI) be assigned to it by the AN. b. The AN sends a UATI-Assignment message to assign a UATI to the AT. c. The AT sends a UATI-Complete message to notify the AN that it has received the UATI-Assignment message. d. If no session exists between the AT and AN, a session is established where protocols and protocol configurations are negotiated, stored and used for communications between the AT and the AN. Refer to TIA/EIA/IS-, Section, Session Layer. e. 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). f. The AT and the AN initiate Point-to-Point Protocol (PPP) and Link Control Protocol (LCP) negotiations for access authentication. Refer to RFC. g. The AN generates a random challenge and sends it to the AT in a Challenge Handshake Authentication Protocol (CHAP) Challenge packet in accordance with RFC. h. When the AN receives the CHAP response packet from the AT, it sends a RADIUS Access-Request message packet on the A interface to the AN Authentication, Authorization and Accounting (AAA) entity (which acts as a RADIUS server) in accordance with RFC-. i. The AN-AAA looks up a password based on the User-name attribute in the A Access-Request and if the authentication passes (as specified in RFC- and RFC-), the AN AAA sends an Access-Accept packet on the A interface. The A Access-Accept contains a RADIUS attribute with Type set to 0 (Callback-Id). Refer to Section.., RADIUS Support. j. The AN returns an indication of CHAP authentication success, to the AT. Refer to RFC. k. The AT indicates that it is ready to exchange data on the packet data stream. (E.g., the flow control protocol for the default packet application bound to the packet data network is in the open state). l. The AN sends an A-Setup-A message to the Packet Control Function (PCF) and starts timer T A- setup, to establish the A-Connection. The A-Setup-A message shall not be sent before the AT indicates that it is ready to exchange data on the access stream, as identified in step e. m. The PCF recognizes that no A0 connection associated with the AT is available and selects a PDSN. The PCF sends an A-Registration Request message to the PDSN which includes the Mobility Event Indicator (MEI) within the Vendor/Organization Specific Extension. The PCF starts timer T regreq. n. The A-Registration Request is validated and the PDSN accepts the connection by returning an A-Registration Reply with an accept indication and Lifetime set to the configured T rp. Both the PDSN and the PCF create a binding record for the A0 connection. The PCF stops timer T regreq. o. When the AN receives the A-Connect-A message it stops timer T A-setup. p. PPP connection establishment procedure and optional Mobile IP Registration on the PPP connection are performed between the AT and the PDSN. Refer to RFC. q. At this point the connection is established and packet data can flow between the AT and the PDSN. 0 -

19 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version.. AT Originates xev-do Session - Unsuccessful Authentication This section describes the call flow for an unsuccessful AT call origination in the AN, due to authentication failure. AT AN AN AAA PCF PDSN time UATI-Request UATI-Assignment a b UATI-Complete c Session Establishment d AT Ready to Exchange Data on Access Stream e PPP and LCP Negotiation f CHAP Challenge - Response g A Access-Request A Access-Reject h i CHAP - Authentication Failure j SessionClose SessionClose k l 0 0 Figure..- Initial AT Origination (with Session Establishment and Key Exchange) a. The AT sends a UATI-Request message to request that a UATI be assigned to it by the AN. b. The AN sends a UATI-Assignment message to assign a UATI to the AT. c. The AT sends a UATI-Complete message to notify the AN that it has received the UATI-Assignment message. d. If no session exists between the AT and AN, a session is established where protocols and protocol configurations are negotiated, stored and used for communications between the AT and the AN. Refer to TIA/EIA/IS-, Section, Session Layer. e. 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). f. The AT and the AN initiate PPP and LCP negotiations for access authentication. Refer to RFC. g. The AN generates a random challenge and sends it to the AT in a CHAP Challenge packet in accordance with RFC. h. When the AN receives the CHAP response packet from the AT, it sends a RADIUS Access-Request message packet on the A interface to the AN AAA (which acts as a RADIUS server) in accordance with RFC-. -

20 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00 i. The AN-AAA looks up a password based on the User-name attribute in the A Access-Request and if the authentication fails (as specified in RFC- and RFC-), the AN AAA sends an Access- Reject packet on the A interface. Note: For ANs that perform access authentication, the network requires that no use of a dedicated resource, such as access to a PDSN, be allowed if authentication fails. j. The AN returns an indication of CHAP authentication failure, to the AT. Refer to RFC. k. The AN sends a SessionClose message to the AT, to close the session. l. The AT responds with a SessionClose message. 0 -

21 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version.. AT Originates with a Pre-existing xev-do Session This section describes the origination call flow for when the AT has already established a session. AT AN PCF PDSN time Connection Establishment a A-Setup-A b T A-setup A-Connect-A c Transmitting Packet Data d 0 Figure..- AT Origination (Session is Already Established) a. If the AT has data to send, the AT initiates connection establishment procedures with the AN. The AN assigns a Forward Traffic Channel, Reverse Power Control Channel and Reverse Traffic Channel. Refer to TIA/EIA/IS-, Section..., Connection Setup State. b. After the traffic channel is established, the AN sends an A-Setup-A message to the PCF and starts timer T A-setup, to establish the A-Connection. c. When the AN receives the A-Connect-A message it stops timer T A-setup. Refer to TIA/EIA/IS- 00-A, Section..., Network Initiated Call Re-Activation from Dormant State. d. At this point the connection is established and packet data can flow between the AT and the PDSN. -

22 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00. Data Delivery This section describes the call flows associated with AT terminated and AT originated data delivery... Data Delivery - AT Terminated This section describes the call flow associated with AT terminated data delivery. In this scenario, it is assumed that the AT has already established a session, however it does not have a connection established. AT AN PCF PDSN time Transmitting Packet Data a A-BS Service Request b T bsreq A-BS Service Response c Page Message d Connection Establishment e A-Setup-A T A-setup A-Connect-A Transmitting Packet Data f g h 0 0 Figure..- AT Terminated Data Delivery a. The PCF determines that packet data is available for delivery to the AT. b. The PCF sends an A-BS Service Request message to the AN in order to request packet service, and starts timer T bsreq. c. The AN responds with an A-BS Service Response. The PCF stops timer T bsreq upon receipt of the A-BS Service Response message. d. The AN sends a Page Message to the AT, on the control channel. e. If the AT has data to send, the AT initiates connection establishment procedures with the AN. The AN assigns a Forward Traffic Channel, Reverse Power Control Channel and Reverse Traffic Channel. Refer to TIA/EIA/IS-, Section..., Connection Setup State. f. After the traffic channel is established, the AN sends an A-Setup-A to the PCF and starts timer T A- setup, to establish the A-Connection. g. When the AN receives the A-Connect-A message it stops timer T A-setup. h. At this point the connection is established and packet data can flow between the AT and the PDSN. -

23 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version.. Data Delivery - AT Originated AT originated data delivery is described in AT call originations. Refer to section.., AT Originates with a Pre-existing xev-do Session.. Connection Tear-Down This section describes the call flows associated with a xev-do connection release... Connection Tear-Down on xev-do Network - Initiated by the AT. This section describes the call flow associated with a connection release initiated by an AT. AT AN PCF PDSN time Connection Tear-Down (Initiated by the AT) A-Release-A a b T rel A-Release-A Complete c 0 Figure..- AT Initiated Connection Tear-Down a. The AT initiates xev-do connection tear-down. Refer to TIA/EIA/IS-, Section, Connection Layer. b. The AN sends an A-Release-A message with a Cause value set to Packet call going dormant, to the PCF to instruct the PCF to release the A connection. The AN starts timer T rel. c. The PCF initiates procedures for releasing the A connection and sends an A-Release-A Complete message to the AN. The AN stops timer T rel. At this time, A0 connection for this call is retained. -

24 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00.. Connection Tear-Down on xev-do Network - Initiated by the AN/PCF. This section describes the call flow associated with a connection release initiated by the AN/PCF. AT AN PCF PDSN time A-Disconnect-A A-Release-A T discon a b T rel A-Release-A Complete c Connection Tear-Down (Initiated by the AN) d 0 Figure..- AN/PCF Initiated Connection Tear-Down a. When the PCF decides to release the connection, the PCF sends an A-Disconnect-A message to the AN and starts timer T discon. In the case where the AN initiates connection release, this step is omitted. b. The AN initiates release of the A connection by transmitting an A-Release-A message and starts timer T rel. The PCF stops timer T discon if it is running. c. The PCF acknowledges the A-Release-A message by returning an A-Release-A Complete message. The AN stops timer T rel. d. The AN may initiate xev-do connection tear-down. Refer to TIA/EIA/IS-, Section, Connection Layer. -

25 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version. Session Tear-Down This section describes the call flows associated with a xev-do session release... Session Tear-Down - Initiated by the AT This section describes the call flows associated with a session release initiated by an AT. It is assumed that the A connection is already established. AT AN PCF PDSN time Session Tear-Down (Initiated by the AT) a A-Release-A b A-Registration Request (Lifetime=0, Acct data) c T rel T regreq A-Registration Reply (Lifetime=0, Accept) d A-Release-A Complete e 0 Figure..- AT Initiated Session Tear-Down a. The AT initiates xev-do session tear-down. Refer to TIA/EIA/IS-, Section, Session Layer. b. After the AN closes the xev-do session, the AN sends an A-Release-A message with a Cause value set to Normal Call Release, to the PCF to instruct the PCF to release the associated dedicated resource and releases the associated A0 connection. The AN starts timer T rel. c. The PCF sends an A-Registration Request message to the PDSN with a Lifetime timer value of zero to close the A0 connection. Accounting data is included in the message. The PCF starts timer T regreq. Refer to TIA/EIA/IS-00-A, Section..., Packet Data Service Session Clearing - MS Initiated. d. The PDSN stores the accounting data for further processing and responds with an A-Registration Reply to complete the release of the A0 connection. The PCF stops timer T regreq. e. The PCF sends an A-Release-A Complete message to the AN. The AN stops timer T rel. 0 -

26 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00.. A0 Tear-Down - Initiated by the PDSN This section describes the call flow associated with an A0 release initiated by the PDSN. AT AN PCF PDSN time A-Registration Update T regupd A-Registration Acknowledgement A-Registration Request (Lifetime=0) a b c T regreq A-Registration Reply (Lifetime=0, accept) d A-Disconnect-A e T discon T rel A-Release-A A-Release-A Complete f g 0 Figure..- PDSN Initiated A0 Tear-Down a. The PDSN initiates closure of the A0 connection by sending an A-Registration Update message to the PCF. The PDSN starts timer T regupd. b. The PCF responds with an A-Registration Acknowledge message. The PDSN stops timer T regupd. c. The PCF sends an A-Registration Request message with Lifetime set to zero, to the PDSN. The PCF starts timer T regreq. d. The PDSN sends an A-Registration Reply message to the PCF. The PCF closes the A0 connection for the AT and stops timer T regreq. e. The PCF sends an A-Disconnect-A message to the AN and starts timer T discon. f. The AN initiates release of the A connection by transmitting an A-Release-A message and starts timer T rel. The PCF stops timer T discon. g. The PCF acknowledges the A-Release-A message by returning an A-Release-A Complete. The AN stops timer T rel. -0

27 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version.. Radio Session Tear-Down - Initiated by the AN. This section describes the call flow associated with a session release initiated by the AN. AT AN PCF PDSN time Session Tear-Down (Initiated by the AN) a A-Release-A b A-Registration Request (Lifetime=0) c T rel T regreq A-Registration Reply (Lifetime=0, accept) d A-Release-A Complete e 0 Figure..- AN Initiated Radio Session Tear-Down a. The AN initiates xev-do session tear-down. Refer to TIA/EIA/IS-, Section, Session Layer. b. The AN sends an A-Release-A message with a Cause value set to Normal Call Release, to the PCF to instruct the PCF to release the associated dedicated resource and releases the associated A0 connection. The AN starts timer T rel. c. The PCF sends an A-Registration Request message with Lifetime set to zero, to the PDSN. The PCF starts timer T regreq. d. The PDSN sends an A-Registration Reply message to the PCF. The PCF closes the A0 connection for the AT and stops timer T regreq. e. The PCF sends an A-Release-A Complete message to the AN. The AN stops timer T rel. -

28 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00. Dormant Handoff of xev-do AT between ANs - Served by the Same PDSN This section describes the call flows associated with AT dormant handoff between ANs... AN-AN Dormant Handoff with Successful Retrieval of Session Information This section describes the call flow associated with a dormant handoff between ANs when the session information is successfully retrieved over the A interface. AT Target AN Target PCF Source AN Source PCF PDSN time UATI-Request a A-Session Information Request b T Areq A-Session Information Response c UATI-Assignment UATI-Complete d Location Update Procedures e A-Session Information Confirm f A-Setup-A g A-Registration Request (Lifetime, MEI) h T regreq A-Registration Reply (Lifetime, accept) i A-Registration Update j T A-setup A-Registration Acknowledge T regupd k A-Registration Request (Lifetime=0) T regreq A-Registration Reply (Lifetime=0, accept) l m A-Release-A-Complete n Figure..- Inter-PCF/Intra-PDSN Dormant AN-AN HO - Successful Operation 0 a. The target AN receives a UATI-Request from the AT. b. The target AN sends an A-Session Information Request message to the source AN to request the session information for the AT. The A-Session Information Request message shall include the received UATI, the Security Layer Packet and Sector ID. The target AN starts timer T Areq. c. The source AN validates the A-Session Information Request and sends the requested session information of the AT to the target AN in an A-Session Information Response message. d. The AN sends a UATI-Assignment to the AT. The AT confirms the receipt of the UATI with a UATI-Complete. The UATI-Assignment may contain a new UATI or use the UATI received in the UATI-Request message. This step can occur anytime after receipt of the UATI-Request message. -

29 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version 0 0 e. The Location Update procedures may be used to retrieve the PANID information for sending to the PCF / PDSN. f. The target AN sends an A-Session Information Confirm to the source AN to indicate that the target AN has received the session information. The target AN stops timer T Areq. Upon receipt of the A- Session Information Confirm message the source AN deletes the AT session information in question. g. The target AN sends an A-Setup-A message, with Data Ready Indicator set to 0, to the target PCF and starts timer T A-setup. h. The target PCF selects the PDSN to connect to using the PDSN address provided in the A-Session Information Response message or using PDSN selection algorithms as specified in TIA/EIA/IS-00, and sends an A-Registration Request message to the PDSN. The A-Registration Request message includes the Mobility Event Indicator (MEI) within the Vendor/Organization Specific Extension. The target PCF starts timer T regreq. Refer to TIA/EIA/IS-00-A, Section..., Inter-PCF Dormant Handoff - Mobile Continues to be Served by the Serving PDSN. i. The A-Registration Request is validated and the PDSN accepts the connection by returning an A-Registration Reply with an accept indication and the Lifetime set to the configured T rp value. If the PDSN has data to send, it includes the Data Available Indicator within the Vendor/Organization Specific Extension. The A0 connection binding information at the PDSN is updated to point to the target PCF. The target PCF stops timer T regreq. j. The PDSN initiates closure of the A0 connection with the source PCF by sending an A-Registration Update message. The PDSN starts timer T regupd. k. The source PCF responds with an A-Registration Acknowledge message. The PDSN stops timer T regupd. l. The source PCF sends an A-Registration Request message with Lifetime set to zero, to the PDSN. The source AN/PCF starts timer T regreq. m. The PDSN sends an A-Registration Reply message to the source PCF. The source PCF closes the A0 connection for the AT and stops timer T regreq. n. The target PCF responds to the target AN with an A-Release-A-complete message. The AN stops timer T A-setup. 0 -

30 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00.. Dormant AN-AN Handoff with Session Information Transfer Failure This section describes the call flow associated with a dormant handoff between ANs when the session information can not be retrieved successfully from the source AN. AT Target AN Target PCF Source AN Source PCF AAA-AN PDSN time UATI-Request a T Areq UATI-Assignment UATI-Complete Location Update Procedures A-Session Information Request A-Session Information Reject b c d e A-Setup-A Access Authentication A-Registration Request (Lifetime, MEI) f g h T regreq A-Registration Reply (Lifetime, accept) i A-Registration Update j T A-setup T regupd A-Registration Acknowledge k A-Release-A-Complete T regreq A-Registration Request (Lifetime=0) A-Registration Reply (Lifetime=0, accept) l m n Figure..- Inter-PCF/Intra PDSN Dormant AN-AN HO - Session Info Transfer Failure 0 a. The target AN receives a UATI-Request from the AT. b. The target AN sends an A-Session Information Request message to the source AN to request the session information for the AT. The A-Session Information Request message shall include the received UATI and the Security Layer Packet. The target AN starts timer T Areq. c. The source AN cannot validate the A-Session Information Request or does not have the requested AT session information and sends an A-Session Information Reject message to the target AN. The target AN stops the timer T Areq. d. The target AN sends a UATI-Assignment to the AT with a new UATI. The AT confirms that it has received the UATI with a UATI-Complete message. This step can occur anytime after receipt of the UATI-Request message. e. The Location Update procedures may be used to retrieve the PANID information for sending to the PCF / PDSN. -

31 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version 0 0 f. Since no session exist between the AN and AT, a new session is established. The AT opens an access stream for access authentication. If access authentication is enabled/supported at the target AN, it shall initiate a PPP on the access stream. The AT performs an access authentication via CHAP / RADIUS towards the AN-AAA. The AN shall use the MN ID received from the AN-AAA in the A Access-Accept, in messages on the A/A interfaces. Refer to Section., A (AN-AN AAA) Interface. g. The target AN transmits an A-Setup-A message to target PCF with Data Ready Indicator set to 0 to establish an A connection and starts timer T A-setup. h. The target PCF selects a PDSN for this call using PDSN selection algorithms as specified in IS-00. The target PCF sends an A-Registration Request message to the selected PDSN. The A- Registration Request includes the Mobility Event Indicator (MEI) within the Vendor/Organization Specific Extension. The PCF starts timer T regreq. Refer to TIA/EIA/IS-00-A, Section..., Inter- PCF Dormant Handoff - Mobile Continues to be Served by the Serving PDSN. i. The A-Registration Request is validated and the PDSN accepts the connection by returning an A-Registration Reply with an accept indication and the Lifetime set to the configured T rp value. If the PDSN has data to send, it includes the Data Available Indicator within the Vendor/Organization Specific Extension. The A0 connection binding information at the PDSN is updated to point to the target PCF. The target PCF stops timer T regreq. j. The PDSN initiates closure of the A0 connection with the source PCF by sending an A-Registration Update message. The PDSN starts timer T regupd. k. The source PCF responds with an A-Registration Acknowledge message. The PDSN stops timer T regupd. l. The source PCF sends an A-Registration Request message with Lifetime set to zero, to the PDSN. The source AN/PCF starts timer T regreq. m. The PDSN sends an A-Registration Reply message to the source PCF. The source PCF closes the A0 connection for the AT and stops timer T regreq. n. The target PCF responds to the target AN with an A-Release-A Complete message. The AN stops timer T A-setup. 0 -

32 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00 No text. -

33 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version 0 xev-do and IS-000 IOS Transition Call Flows This section describes the call flows associated with handoffs between xev-do and TIA/EIA/IS-000 systems, for hybrid MS/ATs.. Dormant/Idle (Voice or Packet) Cross System Handoff - Served by the Same PDSN. This section describes the call flows for dormant/idle handoffs between xev-do and TIA/EIA/IS-000 systems... Dormant/Idle IS-000 Handoff to Idle xev-do - Existing Session This section describes the call flow associated with an MS/AT idle handoff from an IS-000 to a xev- DO system, when the xev-do system supports unsolicited Location Notification messages. Refer to TIA/EIA/IS-. Based on the MS/AT changing to a different ANID or for other reasons, a dormant handoff from IS-000 to idle xev-do is determined to be required. In this scenario, it is assumed that the MS/AT has already established a 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 xev-do system. MS/AT Target AN Target PCF Source BSC/PCF PDSN time Location Update Procedures A-Setup-A a b A-Registration Request (Lifetime, MEI) c T regreq A-Registration Reply (Lifetime, accept) d A-Registration Update e T A-setup T regupd A-Registration Acknowledge f A-Registration Request (Lifetime=0) g A-Release-A Complete T regreq A-Registration Reply (Lifetime=0, accept) Figure..- MS/AT Idle Handoff from IS-000 to xev-do - Existing Session h i 0 a. The change of AN is indicated by the Location Update procedures as defined in TIA/EIA/IS-. b. The target AN sends an A-Setup-A message to the target PCF and starts timer T A-setup. c. The target PCF sends an A-Registration Request message to the PDSN. The A-Registration Request message includes the MEI, the PANID of the source PCF and the Current Access Network Identifiers (CANID) of the target PCF, within the Vendor/Organization Specific Extension. The target PCF starts timer T regreq. d. The A-Registration Request is validated and the PDSN accepts the connection by returning an A-Registration Reply with an accept indication and the Lifetime set to the configured T rp value. If -

34 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, 00 0 the PDSN has data to send, it includes the Data Available Indicator within the Vendor/Organization Specific Extension. The A0 connection binding information at the PDSN is updated to point to the target PCF. The target PCF stops timer T regreq. e. The PDSN initiates closure of the A0 connection with the source BSC/PCF by sending an A-Registration Update message. The PDSN starts timer T regupd. f. The source BSC/PCF responds with an A-Registration Acknowledge message. The PDSN stops timer T regupd. g. The source BSC/PCF sends an A-Registration Request message with Lifetime set to zero, to the PDSN. The source BSC/PCF starts timer T regreq. h. The PDSN sends an A-Registration Reply message to the source BSC/PCF. The source BSC/PCF closes the A0 connection for the MS/AT and stops timer T regreq. i. The target PCF sends an A-Release-A Complete message to the target AN. The target AN stops timer T A-setup. -

35 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version.. Dormant/Idle IS-000 Handoff to Idle xev-do - New Session This section describes the call flow associated with an MS/AT idle handoff from an IS-000 to a xev- DO 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 IS-000 to idle xev-do is determined to be required and the idle MS/AT tunes from IS-000 to xev-do. MS/AT UATI-Request Target AN/PCF Source BSC/PCF Target AN AAA PDSN time a UATI-Assignment b UATI-Complete c Session Establishment d AT Ready to Exchange Data on Access Stream e PPP and LCP Negotiation CHAP Challenge - Response f g A Access-Request A Access-Accept h i CHAP - Authentication Success j Location Update Procedures k AT Ready to Exchange Data on Packet Data Stream T regreq A-Registration Request (Lifetime, MEI) A-Registration Reply (Lifetime, accept) l m n A-Registration Update o A-Registration Acknowledge T regupd p A-Registration Request (Lifetime=0) q T regreq A-Registration Reply (Lifetime=0, accept) r PPP Traffic s 0 Figure..- MS/AT Idle Handoff from IS-000 to xev-do - New Session a. The MS/AT sends a UATI-Request message to request that a UATI be assigned to it by the target AN/PCF. b. The target AN/PCF sends a UATI-Assignment message to assign a UATI to the MS/AT. c. The MS/AT sends a UATI-Complete message to notify the target AN/PCF that it has received the UATI-Assignment message. -

36 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version June, d. Since no session exists between the MS/AT and target AN/PCF, a session is established where protocols and protocol configurations are negotiated, stored and used for communications between the MS/AT and the AN. Refer to TIA/EIA/IS-, Section, Session Layer. e. 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). f. After session configuration the MS/AT initiates PPP and LCP negotiations for access authentication. Refer to RFC. g. The target AN/PCF generates a random challenge and sends it to the MS/AT in a CHAP Challenge packet in accordance with RFC. h. When the target AN/PCF receives the CHAP response packet from the MS/AT, it sends a RADIUS Access-Request message packet on the A interface to the AN AAA (which acts as a RADIUS server) in accordance with RFC-. i. The target AN-AAA looks up a password based on the User-name attribute in the A Access- Request and if the authentication passes (as specified in RFC- and RFC-), the AN AAA sends an Access-Accept packet on the A interface. The A Access-Accept contains a RADIUS attribute with Type set to 0 (Callback-Id). Refer to Section.., RADIUS Support. j. The target AN/PCF returns an indication of CHAP authentication success, to the MS/AT. Refer to RFC. k. The change of AN is indicated by the Location Update procedures as defined in TIA/EIA/IS-. l. The AT indicates that it is ready to exchange data on the packet data stream. (E.g., the flow control protocol for the default packet application bound to the packet data network is in the open state). m. The target AN/PCF sends an A-Registration Request message to the PDSN. The A-Registration Request message includes the MEI, the PANID of the source and the CANID of the target PCF, within the Vendor/Organization Specific Extension. If PANID is not sent in step l, the AN/PCF sets all of the fields within the PANID and the CANID to zero. The target AN/PCF starts timer T regreq. n. The A-Registration Request is validated and the PDSN accepts the connection by returning an A-Registration Reply with an accept indication and the Lifetime set to the configured T rp value. If the PDSN has data to send, it includes the Data Available Indicator within the Vendor/Organization Specific Extension. The A0 connection binding information at the PDSN is updated to point to the target AN/PCF. The target AN/PCF stops timer T regreq. o. The PDSN initiates closure of the A0 connection with the source BSC/PCF by sending an A-Registration Update message. The PDSN starts timer T regupd. p. The source BSC/PCF responds with an A-Registration Acknowledge message. The PDSN stops timer T regupd. q. The source BSC/PCF sends an A-Registration Request message with Lifetime set to zero, to the PDSN. The source BSC/PCF starts timer T regreq. r. The PDSN sends an A-Registration Reply message to the source BSC/PCF. The source BSC/PCF closes the A0 connection for the MS/AT and stops timer T regreq. s. PPP traffic flows. 0 -

37 June, 00 SP--000 (TIA/EIA/IS-) xev-do IOS Ballot Version.. Idle xev-do Handoff to Dormant/Idle IS-000 This section describes the call flow associated with an MS/AT idle handoff from a xev-do to an IS- 000 system. Based on the MS/AT changing to a different ANID or for other reasons, an idle handoff from xev-do to dormant IS-000 is determined to be required. In this scenario, it is assumed that the MS/AT has already established a session, however it does not have a connection established. MS/AT Target BSC/PCF Source AN/PCF MSC PDSN time Origination (DRS='0') a BS Ack Order b Complete L Info CM Service Request c T 0 Assignment Request d T regreq A-Registration Request (Lifetime, MEI) T 0 A-Registration Reply (Lifetime, accept) e f T 0 Assignment Failure Clear Command Clear Complete g h i A-Registration Update j T regupd A-Registration Acknowledge k A-Registration Request (Lifetime=0) l T regreq A-Registration Reply (Lifetime=0, accept) m 0 Figure..- MS/AT Idle Handoff from a xev-do to an IS-000 System a. Upon tuning to the IS-000 system, the MS/AT transmits an Origination Message, with layer acknowledgment required, over the access channel of the air interface to the target BSC/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 A-Registration Request message that the target BSC/PCF sends to the PDSN. b. The target BSC/PCF acknowledges receipt of the Origination Message with a Base Station Acknowledgment Order to the MS/AT. c. The target BSC/PCF constructs a CM Service Request message, places it in the Complete Layer Information message, sends the message to the MSC and starts timer T 0. d. The MSC sends an Assignment Request message to the target BSC/PCF requesting assignment of radio resources and starts timer T 0. The BSC/PCF stops timer T 0. -