3GPP2 Network Evolution:UMB->HRPD Handoff

October 16, 2007Qualcomm Inc.

Contact: Jun WangNotice

Contributors grant a free, irrevocable license to 3GPP2 and its Organization Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner’s name any Organizational Partner’s standards publication even though it may include portions of the contribution; and at the Organization Partner’s sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner’s standards publication. Contributors are also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution. This document has been prepared by the contributors to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on the contributors. Contributors specifically reserve the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the contributors other than provided in the copyright statement above.

UMB-HRPD Handoff Scenarios• Scenario 1: While the AT is in UMB, the AT has both PPP

and TFT established with PDSN• Scenario 2: While the AT is in UMB, the AT has no PPP

and TFT established with PDSN– Scenario 2.1: AT needs to pre setup PPP and TFT while AT is in

UMB (called Pre PPP Setup)• Active Handoff for real time services

– Scenario 2.2: AT can setup PPP and TFT after AT is handoff to UMB (Called Post PPP Setup)

• Active Handoff for best effort traffic• Dormant handoff

Active handoff between UMB and HRPD for real time services

• Handoff for real-time IP applications (such as VoIP) when UMB coverage is not yet ubiquitous

• Desirable objectives:– Enable low interruption handoff between UMB and HRPD without

requiring changes to deployed HRPD RANs and HRPD Core

– Enable commonality:• On Handoff from UMB to any technology (including HRPD)• Between any technology handing off to HRPD, and • On handoff from any Technology (including HRPD) to UMB

UMB to HRPD Active Handoff Overview• Proposal in this presentation assumes that the AT can only transmit

in a single technology (UMB/HRPD/1x) at any given time but may be able to monitor pilot from multiple technologies– Simultaneous transmission on multiple technologies increase

cost/complexity of the ATs

– Transmit power at the AT is also subjected to radiation safety regulation

– Therefore, UMB needs to support tunneling of HRPD signaling messages in order to prepare for handoff to minimize interruption to real-time applications while the AT is in UMB

• The AT can acquire HRPD pilot by one of the following methods– Tune away mechanism specified in the UMB air interface

– Using one of the Rx chains in a multiple Rx chain AT

Handoff Architecture

AT

eBS

HRPD RNC/PCF PDSN

AGW

SRNC

HA/LMA PCRF AAA

A10/A11

HRPD

UMB Note: The interfaces that do not belongs to TSG-X spec are not shown.

Alternative 1 CMIP Based Approach

AT UMB eBS/SRNC HRPD AN HAPDSN

12. AT performs MIPv4 or MIPv6 registration

Data Data Data

2. Data 2. Data 2. Data

AGW

1. AT starts from UMB

11. AT tunes to HRPDand completes HRPD connection setup

6. HRPD AN setup A8/A9 with PCF and PCF Setup A10.A11 with PDSN

3. HRPD Pilot Detected

4. HRPD Session Establishment

8. HO to HRPD

10. Connection Close

13. SIP Reinvite

CSCF

5. HRPD AN PPP Establishment

7. PPP Establishment and TFT Establishment between AT and PDSN

9. Traffic Channel Assignment

MIP Optimization• The AT can send MIP RRQ before step 12 (i.e., before

leaving the UMB network).• This allows MIP binding and air link HRPD connection

setup to progress in parallel• When the AT established HRPD connection, it sends

another MIP RRQ• This way the FL packets will be diverted to HRPD earlier

Alternative 2 PMIP Based Approach (Pre PPP Setup)

AT UMB eBS/SRNC HRPD AN LMAPDSN

12. A9/A11 Signlaing“PMIP” Indicator

Data Data Data

2. Data 2. Data 2. Data

AGW

1. AT starts from UMB

11. AT tunes to HRPDand completes HRPD connection setup

3. HRPD Pilot Detected

10. Connection Close

CSCF

13. PMIP Binding

6. HRPD AN setup A8/A9 with PCF and PCF Setup A10.A11 with PDSN

“No PMIP” Indicator

4. HRPD Session Establishment

8. HO to HRPD

5. HRPD AN PPP Establishment

7. PPP Establishment and TFT Establishment between AT and PDSN

9. Traffic Channel Assignment

Alternative 2 PMIP Based Approach (Post PPP Setup)

AT UMB eBS/SRNC HRPD AN LMAPDSN

Data Data Data

2. Data 2. Data 2. Data

AGW

1. AT starts from UMB

3. HRPD Pilot Detected

4. Connection Close

CSCF

10. PMIP Binding

8. HRPD AN setup A8/A9 with PCF and PCF Setup A10.A11 with PDSN

“No PMIP” Indicator

6. HRPD Session Establishment

7. HRPD AN PPP Establishment

9. PPP Establishment and TFT Establishment between AT and PDSN

5. HO to HRPD

Comparison between PMIP and CMIP Based Solution

CMIP• No standard changes• No change to the existing PDSN in

HRPD system• No Change to the existing HA in

HRPD system• Same solution applies to pre PPP

setup and post PPP setup from PDSN perspective

• Same solution applies to handoff from UMB to HRPD and from HRPD to UMB

• Same solution applies to different technologies handoff from core perspective

– HRPD <-> other Technologies– UMB <-> other Technologies

PMIP• Need to upgrade A9/A11 Signaling

Interfaces– Need to upgrade BSC, PCF, and

PDSN to support the new signaling

• Need to upgrade PDSN for support of PMIP

• Need to upgrade HA or add LMA to support PMIP

• PMIP Triggers to pre-setup PPP and post-setup PPP is different

• PMIP Triggers for different directions (UMB-> HRPD and HRPD-> UMB) may be different

Dormant Handoff between HRPD and UMB

• Dormant Handoff:– From UMB to HRPD:

• No Difference from HRPD inter-PDSN dormant handoff.

– From HRPD to UMB:• No Difference from UMB inter-AGW idle handoff.

Conclusion• No AGW-PDSN Interface is needed for UMB-HRPD handoff• No PDS standard impact if CMIP is used• If PMIP is used:

– Need to upgrade A9/A11 Signaling interface• Need to change HRPD AN, PCF, and PDSN

– Need to upgrade HRPD PDSN to support PMIP

• If CMIP is used, the same solution can be used for both directions (HRPD to UMB handoff and UMB to HRPD handoff)

• If CMIP is used, the same solution can be used for handoff between UMB and other technology

• If CMIP is used, the same solution can be used for handoff between HRPD and other technology

• Recommend to adopt the concept