Overview of TSG-X Femto Standardization Activities 3GPP2 TSG-X Betsy Covell, Chair 31 March 2009

3GPP2 Standards Architecture – Key Aspects Reflects SIP/IMS approach for 1x circuit services Voice services Supplementary services (SMS, etc.) Emergency and location services Packet data service model Reuse existing interfaces (A10/A11) to PDSN from FAPs “Flat” model with packet data service terminated in FAPs is in roadmap for second release of specifications Security architecture using IPsec/IKEv2 Certificates with simple authentication model Basic IPsec/IKEv2 profiles Local IP Access (Local Breakout) Access to owner’s local home network Packet Data Service traffic can flow directly to home Internet service Access to home network resources when mobile device is operating on the macro system via the user’s home femtocell

3GPP2 Reference Architecture – 1x Circuit

3GPP2 Reference Architecture – Packet Data (Legacy)

3GPP2 Reference Architecture – Packet Data (Flat)

TSG-X Femtocell-Related Specifications Packet Data Service pieces – X.P0059 Packet data service aspects for 1x and EV-DO SIP/IMS-based 1x legacy voice service Basic management object contents (Proposed) Outline for X.P0059: X.P0059-000 – Femto Network Overview and Architecture X.P0059-100 – Femto Network Specification X.P0059-200 – 1xRTT Femto Services X.P0059-300 – Femto Configuration X.P0059-400 – 1xRTT Femto Supplementary Services

Additional Material for Discussion on Femtocell Management

Femtocell Device Management TSG-X PDS proposed using TR-069 for femto cell auto-configuration Each TSGs (TSG-X, TSG-A and TSG-C) will specify auto-configuration parameters within their scopes X.P0059-300 plans to contain at least network related auto-configuration parameters Whether other TSGs auto-configuration parameters will be contained in this document are TBD TR-069 family of standards defined by Broadband Forum to manage “touch-free” CPE devices in a very general manner Discovery Configuration Alarming/Event reporting Etc. Some access technologies agonistic auto configuration parameters may be reused by 3GPP2 What 3GPP/FF/BBF-defined HNB/HeNB auto-configuration parameters can be reused are for further studies Examples: IPsec, timing, GPS/location, etc. 3GPP2 specific auto configuration parameters are FFS Liaison Relationship with Broadband Forum is under investigation

Plan of Introducing TR-069 FMS is the TR-069 server FAP is the TR-069 Client FAP and FMS communicates each other through IPsec tunnel between FAP and FGW 8

FAP Data model Structure FapDevice is a profile in the data model General aspect to control the FAP’s operation. General aspect to configure the FAP for proper operation. General aspect to monitor the operation of the FAP. Data model definition exists in the current draft that can be potential used for 3GPP2.. Open area. Need to add for 3GPP2 9 9

TR069 Procedures for femto During FAP initialization, TR-069 is used for Location Verification FAP Provisioning Parameters for these steps are being defined in each TSG These parameters will have to be modeled in the BBF data model containers

Potential External Dependencies or Liaison Activities Definition of FAP management architecture TR-069-based approach Expected that management objects will be converted into TR-069 objects by the Broadband Forum (similar to 3GPP management architecture) cdma2000 1x and EV-DO objects within Femto Forum management object framework Re-use of major portions of management objects that are common (e.g., Security Gateway-related objects) Consider working with 3GPP on SIP/IMS femto architecture Ensure 1x-specific services are supported by 3GPP2 standards Other areas of common interest with Femto Forum and 3GPP Local IP Access Regulatory issues TSG-X proposed to manage external liaison relationships for these femtocell activities (with inputs from all TSGs as appropriate)