1. Source: Qualcomm Incorporated Contact: Peerapol Tinnakornsrisuphap, Jun Wang, George Cherian March 1, 2010 Page 1 3GPP2 Femtocells Phase II Standards Notice © 2010. All rights reserved. Qualcomm Incorporated 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. Qualcomm Incorporated is 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 Qualcomm Incorporated 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 Qualcomm Incorporated. Qualcomm Incorporated 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 Alcatel Lucent and Qualcomm Incorporated other than provided in the copyright statement above.

2. Femtocell Standardization Status Phase I of 3GPP2 femtocell specifications have been completed, except for last four documents: S.R0126-0 (System Requirements for femtocell Systems) S.S0132 (Femtocell Security Framework) X.S0059-000, 100, 200 (Femtocell Network Specs) A.S0024-0: Femtocell A interface Spec C.S0005-E (Includes 1x femtocell Air interface enhancement) C.S0024-C (Includes HRPD femtocell Air Interface enhancement) C.S0016-D (Includes PUZL for femtocell OTA provisioning) X.S0059-400 (Femtocell Supplementary Services) C.S0032-C (Includes Femtocell Minimum Performance Specifications) X.R0063 (Femtocell Management Object) S.R0139 (Femtocell Systems Overview/Guideline) Page 2

3. Highlights of Phase I features The followings are highlights of Phase I features: 1x Femtocell architecture (SIP/IMS) and HRPD Femtocell architecture Security Framework Enhanced System Selection 1x air-interface enhancement for femtocells Mobility support for 1x active and idle handoff between femtocell and macro network HRPD idle handoff between femtocell and macro network Local IP Access and Remote IP Access services Open TR-069 provisioning interface along with management objects definitions Femto Minimum Performance Specification Page 3

4. New Features/Capabilities in Phase II Work Items 3GPP2 System Enhancements for Femtocell Support Phase II (00242) includes but not limited to: Cdma2000-1x IOS based architecture IMS based architecture enhancements Backhaul optimization: Header compression and other mechanisms to reduce backhaul capacity requirements. Femto Access Control Enhancements: Provides full support of this feature, for example, enterprise femto access control. Mobility enhancements: cdma2000-1x hand-in improvements, HRPD active hand-in, femto-femto handoff, etc. Femto flatter architecture: Support of a flatter architecture (for example, by bringing PDSN function on to the FAP). Synchronization enhancements: Mechanisms for synchronization that does not depend on GPS or when GPS signal is inadequate. Enhanced interference management: Support schemes that may require communication between femto cells or between femto cell and macro cell to reduce interference. Other new features such as enterprise features, femto zone services, etc. Page 4

5. Femtocell Phase II Features Requested by CDG Femtocell Phase II Features received from CDG (see X00-20100125-026A TSG-X Work Item Priority Survey) Enhancements to support services (a.ka. Femtozone services) available through access via the FAP (Femtocell Access Point) Enhancements for the management of Femto systems in the mass market (e.g. enhanced auto-configuration, user- profile driven customization etc.) Deployment guidelines for the mass market IMS based architectural enhancements towards an all IP NGN Mobility enhancements to support 1x and HRPD active hand-in, FAP-to-FAP handover Flat architecture: Adoption PDSN functions at the FAP Synchronization enhancements in the Femto system, when a GPS signal is weak or absent Enhanced FAP access control (e.g. enterprise FAP access control etc.) Enhanced interference management between FAPs and between FAPs and Macrocells Backhaul optimizations, such as header compression etc. to enhance backhaul utilization. Detection of the loss of IP backhaul to enhance the user-experience by automatically enabling the mobile device to re-tune to another FAP, or to the Macro system Note: The red items above are already covered in current Femtocell Release II WI (see previous page). Page 5

6. Additional Features in Consideration The following additional features may need to be considered: Local and Remote IP Access Enhancements Efficient Routing for Enterprise Femtocells E-UTRAN Interworking Page 6

7. Phase II Family of Specifications The following specifications may be affected as part of femtocell phase II specifications S.S0126 S.S0132 A.S0024 C.S0005 C.S0016 C.S0024 C.S0087 X.S0059 part 000, 100, 200 and 400 X.R0063 S.R0139 Per work item, the target completion for Phase II specifications is Q4 2010 Page 7

8. Femtocell Zone Enablers Scope Femtocell zones allow a user to be recognized at a femtocell and enable the MS presence information at the femtocell to be available to applications Femtocell zone enablers are presence, interaction and association To support femtocell zones in 3GPP2: Develop MS/AT and network based presence indications Define protocols / procedures to update the presence server (using existing presence-application mechanisms) Potential Standard impact A.S0024 X.S0059 Page 8

9. Femtocell Backhaul Bandwidth Optimization Scope Investigate methods for backhaul bandwidth savings Backhaul IPsec traffic tunneling imposes a significant percentage of bandwidth overhead for voice traffic (small payload, frequent packet interval at about 20ms) The problem is more significant for uplink traffic in a typical DSL (128- 256 kbps) Per Phase I specification, a 1x call consumes a peak rate of 78kbps of uplink backhaul (including all headers) Optimize backhaul bandwidth for 1x CS calls Target to support 4 simultaneous calls within 200kbps (uplink) Potential Standard Impact A.S0024 X.S0059 Page 9

10. 1x IOS-based Architecture Support Scope Support for Femtocell 1x IOS based Voice Architecture SIP-based transport is used in Phase I femtocells Support A1/A1p between FGW and MSC/MSCe Support a TBD interface (e.g., A1p) between FGW and FAP Support Femtocell specific enhancements (e.g., FAP registration, active hand-in) to the IOS interfaces Potential Standard impact A.S0024 X.S0059 Page 10

11. Femtocell Access Control Enhancements Scope Provide an efficient and scalable solution to femtocell access control for enterprise femtocell deployment For 1x femtocell architecture, support a centralized femtocell access control in operator’s network entity  In Phase I specification, for HRPD, either FAP or AN-AAA can perform femtocell access control. For 1x, only FAP can perform femtocell access control Investigate a simple solution for the end user with a dynamic user Access Control List provisioning Investigate the relationship between femtocell access control function and emergency services/priority services Potential Standard impact X.S0059 A.S0024 Page 11

12. Local and Remote IP Access Enhancements Scope Investigate an optimized mean to support broadcast IP packets for both LIPA and RIPA Broadcast IP packets are generated frequently in a typical local-area network. Without further optimization, delivering these packets to the AT over LIPA/RIPA can impact femtocell capacity and AT standby time Investigate the possibility of supporting Remote IP Access without using operator’s backhaul It may be possible to establish a direct tunnel between the AT and the femtocell access point, thus offloading operator’s backhaul from RIPA traffic Potential Standard impact X.S0059 Page 12

13. Efficient Routing for Enterprise Femtocells Scope Support efficient routing of 1x voice traffic in an enterprise environment When two 1x MS under different FAPs in the same enterprise network talk to each other, the voice path unnecessarily traverses the backhaul into the operator’s network Regardless of the enterprise topology being used, it is possible to have a solution where traffic can be more efficiently routed while still fully support mobility and supplementary services Potential Standard impact X.S0059 A.S0024 Page 13

14. E-UTRAN interworking Scope Support of eHRPD functionality for FAP Support IP session continuity for eAT/UE between: eHRPD Femtocell and eHRPD macro network E-UTRAN Femtocell and eHRPD macro network eHRPD Femtocell and E-UTRAN macro network Optimized active-handoff support from E-UTRAN-macro to eHRPD Femtocell Enhance the system selection mechanism to allow selection between eHRPD Femtocell/E-UTRAN Macro and E-UTRAN Femtocell/eHRPD macro Potential Standard impact X.P0059 A.S0024 C.S0087 C.S0016 Page 14

15. Femtocell Management Objects Enhancements Scope Add support for Phase II femtocell features into standard 3GPP2 Femtocell Management Objects Improve support for self-configuration of femtocells Potential Standard impact X.R0063 Broadband Forum TR-196 specification Page 15

16. Flatter Architecture Scope Allow PDSN function in femtocell, for example, PPP link is terminated in the FAP. May need to specify a new interface between FAP and FGW May need to add additional functions in FGW Potential Standard impact X.P0059 A.S0024 Page 16

17. Synchronization Enhancements Scope: Provide a mechanism for FAP synchronization that does not depend on GPS or when GPS signal is inadequate Potential Standard impact TBD Page 17

18. IMS Enhancements Scope: Specify full support for supplementary services Allow for individual IMS registration from FAP for each 1x MS Potential Standard impact X.S0059-400 X.S0059-200 Page 18

19. Deployment Guidelines for the Mass Market Scope Provide guidelines for femtocell deployment including both residential and enterprise environment Recommend optimal procedures and parameter settings in femtocell deployment Address the issues that are considered useful in a real world phased deployment scenario Potential Standard impact S.R0139 Page 19

20. Detection of the Loss of IP Backhaul Scope When FAP detects the loss of IP backhaul, allows FAP to indicate the mobile device Enhance the user-experience by automatically enabling the mobile device to re-tune to another FAP, or to the Macro system Potential Standard impact TBD Page 20

21. Mobility Enhancements Scope Support HRPD active hand-in for both legacy terminals and femtocell-enhanced terminals Simplify 1x active hand-in solution for legacy macro BS Current active hand-in solution for femtocell-enhanced terminal requires macro network upgrade for the terminal to convey the target femtocell identity By embedding the target femtocell identity in a pilot report, it is possible to have a solution where macro network upgrade is not needed Support the active hand-in for 1x IOS-based Femtocells Support handoff between femtocells Potential Standard impact A.S0024 C.S0024-C (in V&V) and C.S0005 Page 21

22. Enhanced Interference Management (IM) Techniques Motivation: IM is critical for femtocell deployments Even when femtocells are deployed on a dedicated carrier, beacons can interfere with macro users Need solutions that ensure robust performance for co-channel femto and macro deployments Enhanced IM techniques can complement traditional techniques (e.g. network listen base power calibration) and optimize performance Scope: Enable Enhanced IM using over-the-air (OTA) and/or backhaul signaling OTA based IM to control femto FL interference Idle mobile sends an OTA message using access probes to a restricted (interfering) femtocell upon detecting strong pilot from this femtocell OTA based IM to control RL interference from femtocell users to macro network Femtocell controls max. Tx power of active home mobiles to limit RL interference Backhaul based IM to control femto FL interference Co-ordination between macro base stations and femtocells via backhaul to reduce femtocell interference to macro users Potential Standards Impact C.S0005, C.S0024, A.S0024 Page 22

23. Conclusions The following femtocell Phase II features may impact on TSG-A Femtozone services (Effort: Medium) Backhaul Bandwidth Optimization (Effort: Medium) Enhancements for the management of Femto systems in the mass market (Effort: Medium) Deployment guidelines for the mass market (Effort: High) Enhanced FAP access control (e.g. enterprise FAP access control etc.) (Effort: Medium) Synchronization enhancements (Effort: TBD) Flatter architecture (Effort: High) Cdma2000 1x IOS based architecture (Effort: TBD) Efficient routing for enterprise femtocells (Effort: High) E-UTRAN interworking (Effort: Medium) Mobility Enhancements (Effort: High) Enhanced Interference Management (IM) Techniques (Effort: TBD) Note: Red: Included in CDG list. Blue: In addition included in TSG-S WI. Black: Additional WI. Page 23