Requirement for Proxy Mobile IP tunnel for AGW-eBS data tunnel Qualcomm, Inc. 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.

Introduction For UMB, an access gateway may connect to several eBSs – one of which may be the forward-link serving anchor (FLSA) and/or reverse-link serving anchor (RLSA) IP packets of the AT are forwarded through a tunnel between AGW and eBS There needs to be a signaling interface that moves the tunnel when the AT moves between eBSs under the same AGW –The movement of the tunnel does not have to be perfectly aligned with the eBS that serves the AT since eBS can also tunnel packets between each other if the eBS switch is fast –DAP is the endpoint on UMB RAN side that receives FL data from AGW

Why Proxy Mobile IPv4? The System Requirements Document for Network Evolution for 3GPP2 Networks (S.P0121-0) states, “The Evolved Network shall be designed to maximize the use of standardized IP protocols.” Proxy Mobile IPv4 is similar to A10/A11 interface in HRPD PDSN –Both IPv4 and IPv6 packets can be encapsulated in the same PMIPv4 tunnel –Deployments and interoperability based on Proxy Mobile IPv4 already available

Proxy Mobile IP (PMIP) eBS that is DAP acts as Proxy Mobile Node that registers with the AGW on behalf of the AT The AGW serves as the PMIPv4 Home Agent Packets between AGW-eBS are tunneled in GRE tunnel –To be able to support MIPv4 FA/CoA mode with overlapping addresses, refer to contribution A r0 UMB IP Packet Tunneling and Routing (AHQ) Both AGW and eBS shall support PMIPv4 –Both IPv4 and IPv6 packets are encapsulated in the same tunnel

eBS2 (FLSA) eBS3 (RLSA) eBS1 (DAP) AGW PMIP tunnel (GRE) IPT interface PMIP tunnel (GRE) UMB PMIP tunnel (GRE) Example

Requirements of PMIP tunnel (1) The PMIP Protocol for IPv4 shall uniquely identify per AT PMIP tunnels between the AGW and eBSs in the route set of the AT independent of the any IP address assigned to an AT. The identification (e.g. GRE key) shall be known to the AGW and the eBSs which are members of the route set. Use same GRE keys in both tunnel directions for any eBSs served under the same AGW –Because DAP can quickly be relocated to several eBSs, AGW does not need to bind new keys with the AT frequently In HRPD, PCF handoffs are very infrequent so it is acceptable to have reverse-link GRE key assigned by PCF and have both keys change every PCF handoff –Because is unique, this tuple can be used in IP tunnels between eBSs to identify the ATs so eBSs can also serve multiple AGWs and overlapping address spaces An eBS obtains this information when it was added into the route set, so there is no need to negotiate and manage multiple keys in IP tunnels between eBSs

Requirements of PMIP tunnel (2) PMIP protocol shall not prohibit and shall be subject to any and all security mechanisms determined to be necessary and reasonable by TSG-S WG4 Permanent NAI is used for PMIP-Registration Request/Response messages PMN-HA key is used to protect the PMIP tunnel –Every eBS in the route set obtains the NAI and key from SRNC when it is added to the route set –These information will be used to construct PMIP signaling messages

Requirements of PMIP tunnel (3) Support for multiple CoAs binding should be allowed –Allows RLSA eBS to tunnel packets back directly to AGW to reduce latency –The PMIP protocol for IPv4 shall include a mechanism whereby an eBS in an AT’s route set can indicate to the PMIPv4 HA that it is the forward-link serving eBS The AGW shall be capable of recognizing a mobility event, accept a PMIP registration on behalf of an AT using the same tunnel identifier, and possibly revoke the registration binding of the previous eBS if multiple CoAs are not used

Recommendations Step 1 –Accept and publish the following drafts as 3GPP2 specifications by October 2007 PMIPv4 base draft GRE key extension draft MCoAs draft –Step 2 Request IETF to publish the above drafts as either standard or informational RFC

Backup Slides

Packet Headers (Simple IPv4 AT)