1. HRPD Femto Local IP Access: Overview Peerapol Tinnakornsrisuphap (peerapol@qualcomm.com) Qualcomm October 27 th, 2008 3GPP2 Seoul, Koreapeerapol@qualcomm.com Notice ©2008. All rights reserved. The contributors grants a free, irrevocable license to 3GPP2 and its Organizational 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 all or portions of this contribution; and at the Organizational Partner’s sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner’s standards publication. The 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. The contributors specifically reserves 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.

2. What is Local IP access? Previously called “HRPD Femto Local Breakout” Local IP access provides local IP connectivity from the device connecting through Femto Access Point – yielding similar functionalities to wireless LAN without requiring additional support for WLAN on handset  At the same time, connectivity to operator’s core is still preserved for accessing operator’s specific contents and for supporting seamless handoff of QoS-sensitive services Potential usages  Off-load operator’s traffic from operator’s core networks while AT is connected with Femto AP  Synchronizing/streaming media on device with media servers, printers, etc.  Allow device and Femto AP to be more than “just phone service in poor coverage” Internet Femto / Router ATPDSN Media Printer TV Home Domain Operator’s Backhaul AT in macro network

3. Some Use Cases for Local IP Access 1.Share content between phones, bypassing the macro network 2.Stream video stored on home PC to phone 3.Share and stream music between phone and music player 4.Print photos on phone on a home printer 5.Control home appliances (e.g., A/C) from phone Home Network Internet Air Conditioning

4. Local IP Access (for EV-DO) - Architecture Red = Traffic Traversing Operator’s network  Goal : Allow ATs to be able access services similar to when AT is on macro network  Assumption : There is IPsec tunnel between Femto cell and the wireless operator’s network Blue = IP access to public Internet via Femto  Goal : Traffic can bypass home network to save operator’s resources and improve latency Green = Local IP access to local CN  Goal : AT can communicate with servers at home

5. Local IP Access : Design Reuse EV-DO access stream (i.e., AN- terminated stream) and AN-PPP, which is currently only being used for access authentication, to assign local IP address  Legacy AT will reject the request or drop the request  Same call flow with simple IPv4 address assignment on PDSN-PPP AN-PPP session and IP interface terminate after AT leaves femto AN  AT can try to request the same IP address (e.g., in enterprise environment) Femto AP also configures the AT with the egress filter – for example  Default IP interface is AN-PPP and only packets for operator’s subnet are sent via PDSN  Or default IP interface is PDSN and only packets for local subnet are sent via AN-PPP Operator may control whether to enable local IP access during femto configuration phase A12 will define a RADIUS attribute to control whether local IP access is allowed for a particular AT

6. Local IP Access Protocol Stack

7. Why Femto AP cannot act as “just a pipe” on AN-PPP stream? Q: Why Femto AP needs to know local IP address assigned to AT – not just forwarding any packets from the AT to LAN? A: Femto AP needs to be aware of the local IP address assigned to the AT so that it can defend the IP address for any packet in the subnet for the AT Detailed explanation: Assuming Ethernet, when router/gateway receives IP packet for the AT, it will broadcast ARP Request for resolving Ethernet MAC address associated with local IP address of the AT. The Femto AP needs to respond to the request eventhough the request is not for the IP address of the femto AP.