1. 10/27/2008X50-20081027-0xx-0021 Femto Initialization Aspects: Femto AP Auto- configuration procedures Source: QUALCOMM Inc Chandru Sundarrman csundarr@qualcomm.com Jun Wang jwang@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. 10/27/2008X50-20081027-0xx-0022 Assumptions –The femto system needs to know the location of the FAP before the FAP can be assigned a frequency to transmit on. –The FAP is not pre-provisioned with any of the radio parameters and many of the identities that are unique to the FAP and needs to be configured every time it is powered ON. –The FAP provides service to the MS through the operator’s network and the entities (FGW, CSCF, MFIF, FMS) in the operator’s network need not be the same every time a given FAP connects to the network for a variety of reasons including Load Balancing FAP is moved to a different location and served by different network entities now

3. 10/27/2008X50-20081027-0xx-0023 Initialization Procedures 1x RTT only or 1x RTT/HRPD capable Femto Access point performs the following steps as part of its Initialization procedures –Neighborhood Discovery Mode Neighboring Cells Detection –Both Macro and Femto neighbor cells would be detected –Network Discovery Mode FGW Discovery and IPSEC tunnel establishment FAP auto Configuration by FMS CSCF / MFIF Registration (1xRTT FAP) (A)GPS or AFLT based Location determination

4. 10/27/2008X50-20081027-0xx-0024 Network Discovery Mode: FAP Auto-configuration by FMS –FAP performs a DNS lookup for the FMS over the secure tunnel –FAP connects to FMS through the secure Tunnel and sends its neighborhood information during this auto-configuration stage TR-069 protocol is used over the Fm interface between FAP and FMS –If geographic location of FAP is already known, FMS configures the FAP with location specific radio parameters [freq, ICGI (MSC_ID/ Cell_ID), Sector ID, PN_OFFSET range,…] as well as IP addresses of other network entities [CSCF, AN-AAA, …] The serving FGW / FMS could be different from Default FGW/FMS. If different, FMS will provision this as well. Other configuration related to Local Breakout [Egress packet filter criteria,…] and Handoffs (Neighbor Macro cell IDs (ICGI), Sector IDs, UATI range,…) will also be configured –If AFLT/ A-GPS procedures are to be performed, FMS will provision FAP with IP address of default CSCF to connect to. Default MSC_ID / Cell_ID may be assigned to FAP by FMS during this phase

5. 10/27/2008X50-20081027-0xx-0025 Network Discovery Mode: FAP registration with Serving CSCF / MFIF –FAP connects to the CSCF to perform IMS registration [of FAP] –CSCF authenticates the FAP and performs 3 rd party registration with the MFIF on behalf of FAP. –If FAP location is not precisely known, FAP should establish an IS-801 session to determine its exact location (AGPS / AFLT) and reconnect to FMS in order to be configured with location specific radio parameters –If connected to Serving CSCF/ MFIF, FAP turns on its transmitter now and is ready to serve MS

6. 10/27/2008X50-20081027-0xx-0026 1x CDMA2000 FAP Auto Configuration and Registration with Serving System

7. 10/27/2008X50-20081027-0xx-0027 Auto-Configuration Call Flows: FAP Redirection to serving system

8. 10/27/2008X50-20081027-0xx-0028 –FAP connects to default CSCF and performs IMS registration of FAP. FAP is then registered with default MFIF –Through the default MFIF, FAP will establish an IS-801 session to determine its location (A-GPS) and will re-connect to FMS to perform Network Discovery Mode procedures again to identify the appropriate serving FGW/ FMS/ MFIF if different from the default one –FAP turns on its transmitter now and is ready to serve MS Network Discovery Mode Cont’d: With Location Determination and Redirection to serving system

9. 10/27/2008X50-20081027-0xx-0029 Auto-Configuration Call Flows: FAP Registration, AGPS based location determination using Default system and Redirection to Serving system

10. 10/27/2008X50-20081027-0xx-00210 Recommendations for 3GPP2 FAP Initialization Aspects Network Discovery Mode –Specify FAP auto Configuration using FMS (Fm) in X.S0059-100 (TSG-X PDS) Support TR-069 based Auto configuration procedures over Fm interface Identify FAP Configuration Parameters through a joint TSG effort –CSCF / MFIF Registration of 1xRTT FAP: (Fx1: X.S0059-200) –TSG-X MMD –Specify (A)GPS or AFLT based Location determination as part of Femto Initialization in X.S0059-100/200 –TSG-X PDS and MMD