Inter-AGW HO Notice 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. October 18, 2007 Qualcomm Inc.

Handoff scenarios with different LinkID

3 C-MIPv4 FA-CoA No interface required between AGWs Each Route presents different LinkID because same LinkID from both Routes would require MIPv4 FA in LMA

4 PMIP No interface required between AGWs

Handoff scenarios with same LinkID

6 C-MIPv4 FA-CoA No custom 3GPP2 interface required between AGWs AGW2 simply acts as a router between AGW1 and eBS2 Packets may flow through a router near AGW2 rather than through AGW2 FA anchored in source AGW instead of custom interface between AGWs

7 PMIP No interface required between AGWs AGW2 simply routes packets between AGW1 and eBS2 Packets may flow through a router near AGW2 rather than through AGW2 MAG anchored in source AGW instead of custom interface between AGWs

8 Pure Simple IP No interface required between AGWs AGW2 simply routes packets between AGW1 and eBS2 Packets may flow through a router near AGW2 rather than through AGW2

Handoff scenarios with Dual Anchor

10 Dual Anchor Handoff No special interface required between AGWs other than PMIP interface AGW1 serves as LMA when the AT moves to the AGW2 AGW2 serves as a FA for CMIP Both IP addresses (IP1 and HoA) remains same before and after inter-AGW HO

11 No need for Inter-AGW interface Seamless inter-AGW handoff for all scenarios Less and faster standardization Less development No change to DO PDSN (in case of UMB-DO handoff) Faster, smoother, lower cost upgrade path from DO to UMB