1. 16 June 2009 3GPP2 TSG-X FMOAHG Subject:Femto Management Object Ad Hoc Group Kickoff Date: 16 June 2009 Source: Chair, FMOAHG Airvana Contact: Doug Knisely dknisely@airvana.com 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 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. Airvana, Inc., 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 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.

2. 3GPP2 TSG-X FMOAHG 16 June 2009 Overview Quick overview of approved 3GPP2 management architecture 3GPP2 MO standardization process and liaison relationship with BBF (and FF, if applicable) Proposal for MO spec format and TSG inputs Proposed workplan Proposed process for working with BBF Recommendations

3. 3GPP2 TSG-X FMOAHG 16 June 2009 Proposed Femtocell Management Standardization Process Femto Forum 3GPP RAN3->SA5 3GPP2 TSG-X/A/C-> 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

4. 3GPP2 TSG-X FMOAHG 16 June 2009 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 specification X.S00xx managed under TSG-X PDS, but based on inputs from TSG-A/C/X  This will serve as input to BBF to drive the 3GPP2 AI extensions to TR-196 Normative 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 normative semantic rules for Mos  3GPP2 will document these in a new specification X.S00xx managed under TSG-X PDS, but based on inputs from TSG-A/C/X  FMOAHG will serve as owner of X.S00xx  FMOAHG will handle baselining, R&F, and V&V for X.S00xx

5. 3GPP2 TSG-X FMOAHG 16 June 2009 FMS Role in Femtocell Power-up Initialization Sequence Source: TSG-A A.S0024 working draft. FMS involvement (partial list): Retrieve FAP characteristics (e.g., vendor, model, hw capabilities, etc.) Redirects (via reconfiguration) the FAP to different gateway, FMS, and/or CN elements as needed Downloads basic operating parameters (e.g., bandclasses that should be searched, etc.) Verifies FAP location (e.g., based on GPS, REM results, CRM-provisioned info, DSL line, etc.) Retrieves and/or sets radio operating parameters (auto-configuration) Enables FAP to begin operation and turn on its xmitter

6. 3GPP2 TSG-X FMOAHG 16 June 2009 Example #2 of Input format from 3GPP to BBF InformationDescription / NotePresence3GPP Reference RF informationUARFCNDLUARFCN (DL)M25.104, sec.5.4 32.642 sec. 6.3.11 CPICHRSCPRSCP of CPICHM PSCPrimary Scrambling CodeM32.642 sec. 6.3.11 Broadcast information PLMN Type« GSM-MAP » or « ANSI- 41 » M25.331, sec.10.3.1.12 MCCMobile Country CodeM24.008 32.642 sec. 6.3.10 MNCMobile Network CodeM24.008 32.642 sec. 6.3.10 LACLocation Area CodeM24.008, sec.10.5.1.3 32.642 sec. 6.3.10 RACRouting Area CodeM24.008, sec.10.5.1.12.3 25.413, sec.9.2.3.7 32.642 sec. 6.3.10 CellID M25.331, sec.10.3.2.2 CSG Cell Info OApplicable to Rel.8 compliant cell only. UTRAN Cell Information

7. 3GPP2 TSG-X FMOAHG 16 June 2009 BBF References TR-196 Specification  http://www.broadband-forum.org/technical/download/TR-196.pdf http://www.broadband-forum.org/technical/download/TR-196.pdf XML Data Model  http://broadband-forum.org/cwmp/tr-196-1-0-0.xml http://broadband-forum.org/cwmp/tr-196-1-0-0.xml

8. 3GPP2 TSG-X FMOAHG 16 June 2009 Workplan, Process, and Recommendations

9. 3GPP2 TSG-X FMOAHG 16 June 2009 Proposal for MO Spec Format and TSG Inputs Based on offline discussions with BBF experts, it seems the following format would be appropriate for the 3GPP2 input to BBF:  Format from TR-196 in Example #3  Bibliography for the appropriate 3GPP2 specifications in which detailed information can be found Note: Bibliography information is preserved by BBF in the XML MO definition as well TSG-A/C/X input to the FMOAHG should be in the format in Example 2 (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.S00xx  AHG will ensure consistency of formatting  AHG will perform manual transformation to data types shown in Example #3

10. 3GPP2 TSG-X FMOAHG 16 June 2009 10 Preliminary Draft Workplan 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 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.S00xx containing MOs baselined  November – Transmit X.S00xx to BBF as first draft  January 2010 – X.S00xx enters first pass V&V  January 2010 – Transmit final version of X.S00xx to BBF  March 2010 – X.S00xx enters TSG-X Re-V&V  ~March 2010 – BBF Straw Ballot  June 2010 – X.S00xx published  ~June 2010 – BBF Final Ballot completes

11. 3GPP2 TSG-X FMOAHG 16 June 2009 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)

12. 3GPP2 TSG-X FMOAHG 16 June 2009 Miscellaneous Volunteer editor for X.S00xx -- TBD  QCOM has indicated intent (currently editor of X.S0059-300, which will not be defunct) Preparation of a template document containing the approved input format to be distributed to TSG-A/C/X Please join the femtomoahg email list!

13. 3GPP2 TSG-X FMOAHG 16 June 2009 Recommendations X.S00xx replaces previously planned X.S0059-300, which can be rescinded Discuss, revise, and adopt initial workplan Discuss, revise, and adopt proposed work process with BBF Liaise call for MO inputs to TSG-A/C/X  Process  Schedule, including target deliverables  Template for MO parameters (select a format, verified by BBF) Transmit initial proposal to BBF at meeting week of 14 September  Working relationship and process  Proposed workplan and working relationship