Subject:Proposed Liaison from TSG-X to BBF Date: 21 August 2009 Source: Chair, FMOAHG Airvana Contact: Doug Knisely cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Airvana, Inc., grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and an y modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even tho ugh 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 th e resulting Organizational Partner's standards publication. Airvana, Inc., is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-dis criminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution. This document has been prepared by Airvana, Inc., 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 Airvana, Inc. Airvana, Inc., specifically reserves the right to amend or modify the material contained herein and to any intellectual property of Airvana, Inc.,other than provided in the copyright statement above.

Oct Recommendations for TSG-X Approve Doug Knisely acting as liaison to BBF for ongoing discussions Approved the remainder of this contribution as a 3GPP2 liaison contribution to the BBF meeting week of 14 September 2009

Oct Background 3GPP2 began work on femtocell-related standardization in early 2007 Technical activities were initiated in all 3GPP2 TSGs in late 2007 –System requirements –Security aspects –Air interface (radio) enhancements –Support for legacy 1x circuit services –Packet data services for 1x and HRPD (EV-DO) Throughout 2008, extensive work has been done in all areas Publication expected in Q3-Q4 2009

Oct Overview Quick overview of approved 3GPP2 management architecture 3GPP2 MO standardization process and liaison relationship with BBF Proposal for MO report format and TSG inputs Proposed workplan Proposed process for working with BBF Recommendations

Oct GPP2 Femtocell Architecture – 1x Circuit

Oct GPP2 Femtocell Architecture – Packet Data (1x+DO)

Oct Role of The TR-069 Standard in Femtocell Management (1) Broadband Forum TR-069 universally selected as the framework for femtocell management –Supported by all 3GPP & 3GPP2 vendors and carriers –Endorsed by Femto Forum –Rich set of features Configuration/operation/sw download/logging Scalable & robust –Will be used also in LTE for Home eNB (HeNB) management Management architecture and TR-069 ACS are the backbone of the key femtocell operational and provisioning call flows in 3GPP and 3GPP2 –Discovery –Registration –Redirection to alternate SeGW, ACS, or Femto Gateway –Self-organizing network –Location verification –Provisioning and radio parameter assignments are managed only by ACS –AAA and back-office interfaces are required only on ACS

Oct Proposed Femtocell Management Standardization Process Femto Forum 3GPP RAN3->SA5 3GPP2 TSG-X/A/C/S-> FMOAHG TR-196 Femto Mgmnt Objects Mgmnt Object Framework Broadband Forum 3GPP AI MO Contents (UMTS, LTE) 3GPP2 AI MO Contents (1x, EVDO) 3GPP Specific Procedures (Disc., etc.) 3GPP2 Specific Procedures (Disc., etc.) Mgmnt Object Framework TR-069 Framework

Oct Scope of Work for 3GPP2 Femto MOs Management Object contents –Attributes –Range of values –Structure that is appropriate for 3GPP2 AIs –3GPP2 will document these in a new technical report X.R00xx managed under TSG-X PDS, but based on inputs from TSG-A/C/X/S –This will serve as input to BBF to drive the 3GPP2 AI extensions to TR-196 Definition of procedures that are required for the proper interworking between the FMS (TR-069 ACS) and the FAP(s) –Procedures for discovery, registration, location verification, provisioning, etc. –Sequences/high level call flows for those procedures –Any additional semantic rules for MOs –3GPP2 will document these in a new specification X.R00xx managed under TSG-X PDS, but based on inputs from TSG-A/C/X/S –FMOAHG will serve as owner of X.R00xx –FMOAHG will handle baselining, R&F, and V&V for X.R00xx

Oct Proposed Format for Management Object Input to BBF from 3GPP2 FeatureParameter Range of ValuesWriteDescription Object DefaultReference

Oct Workplan, Process, and Recommendations

Oct Proposal for MO Spec Format and TSG Inputs Based on offline discussions, it seems the following format would be appropriate for the 3GPP2 input to BBF: –Format from TR-196 in previous slide –Bibliography for the appropriate 3GPP2 specifications in which detailed information can be found TSG-A/C/X/S input to the FMOAHG should be in the format in previous example (along with a reference list) –Simple reference numbers in the “reference” column are sufficient and consistent with our conventions –Any additional normative procedures that need to be documented in X.R00xx –AHG will ensure consistency of formatting –AHG will perform manual transformation to data types

Oct Issues for Discussion/Resolution Between BBF and 3GPP2 General workplan and target dates for inputs to BBF and date of publication of TR by BBF –New version of TR-196? [Working assumption in 3GPP2] –New TR? If new version of TR-196, how to coordinate schedule with 3GPP revisions Day-to-day workplan –Propose coordinating conference calls in a similar manner as used between BBF and 3GPP –Technical contacts in BBF to verify that 3GPP2 inputs are technically sound and suitable for use in a BBF TR

Oct Proposed Draft Workplan (1) Preliminary discussions with BBF indicates: –Tentative proposal to incorporate 3GPP2 AI MO extensions into a new version of TR-196 makes sense –They would like to receive inputs from 3GPP2 as early as possible –Prefer to receive preliminary draft of MO contents early –Final (extremely) stable version as a followup –Crude estimate is 6 months from final MO inputs to publication

Oct Proposed Draft Workplan (2) Initial proposal for 3GPP2 workplan: –June – Call for MO inputs from TSG-A/C/X –August – First draft of MO inputs from TSG-A/C/X –November – Harmonized draft of X.R00xx containing MOs baselined –November – Transmit X.R00xx to BBF as first draft –January 2010 – X.R00xx enters first pass V&V –January 2010 – Transmit final version of X.R00xx to BBF –March 2010 – X.R00xx enters TSG-X Re-V&V –~March 2010 – BBF Straw Ballot –June 2010 – X.R00xx published –~June 2010 – BBF Final Ballot completes

Oct Proposed Process for Working with BBF Complete establishment of liaison relationship (secretariat) –Establish document sharing rules –Document sponsorship and working rules for joint calls and/or meetings (e.g., who’s running the meeting under what rules and with which IPR policies) –Negotiate rules for comments provided to/from 3GPP2 from/to BBF Complete establishment of day-to-day working liaison relationship (fmoahg) –Document process and workplan (described earlier) and liaise to BBF at their upcoming meeting in September –Negotiate final format for delivery of MO parameters Add periodic leadership calls between BBF and 3GPP2 to coordinate (esp. after exchanges start occurring)

Oct Recommendations Completion of IPR, document sharing, joint meeting conduct, and other issues between BBF and 3GPP2 Secretariat –Correspondence 8 July 2009 Joint agreement on working relationship and workplan –“Collaboration” relationship –Procedures for submission of comments against BBF straw ballots, etc. –Re-use of text from each others’ specifications Identify points of contact –3GPP2 liaison contact: Doug Knisely –BBF technical and management contacts? Discuss, revise, and adopt proposed work process with BBF