Subject: Proposed Liaison from TSG-X to BBF

Date: 21 August 2009Source: Chair, FMOAHG

AirvanaContact: 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.

Oct 2008 2

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 2008 3

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 2008 4

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 2008 5

3GPP2 Femtocell Architecture –1x Circuit

HLR/AC

MSC

MC

MAP

Mg (SIP)

Fx3

Fx2 (SIP)

AAA

Ma or ISC

(SIP)

MAP

1xMacro

Cell A2

PDE MPC

Fm(TR-096/

196)

ISUP

ISUP

TDM

TDM

Mm (SIP)

ISUPTDM

IPNetwork

Fx2 (SIP)

1x Macro BSC

A1 PSTN

1x

Femto Access Point

SIPUA

MS

MGCF/MGW

IMS

IP MultimediaNetwork

FCS

PSAP

Fx1 (RTP)

FemtoSecurityGateway

FMS

FemtoAAA

Fx1 (RTP)

Fx1 (RTP)

Legend:FCS Femto Convergence ServerFMS Femto Management System

Oct 2008 6

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

Ty

FGW

Femto-AAA

MS/AT1x/

EV-DO

A11

Internet

(P)M

IP

AA

A(A

12

)AN-AAA

AAA

HA/LMA

PDSN

For A12 Device

Authentication

For Femto

Device

Authentication

EV-DOAN

FAP

A1

3

A1

6-1

9

SeGW

A10

BS/AN

PCRF

FMS

Fm

(TR

-0

96

/1

96

)

Oct 2008 7

Role of The TR-069 Standard inFemtocell 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 2008 8

Proposed Femtocell ManagementStandardization Process

FemtoForum

3GPPRAN3->SA5

3GPP2TSG-X/A/C/S->

FMOAHG TR-196Femto Mgmnt Objects

Mgmnt ObjectFramework

BroadbandForum

3GPP AI MOContents

(UMTS, LTE)

3GPP2 AI MOContents

(1x, EVDO)

3GPP SpecificProcedures(Disc., etc.)

3GPP2 SpecificProcedures(Disc., etc.)

Mgmnt ObjectFramework

TR-069Framework

Oct 2008 9

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 2008 10

Proposed Format for Management Object Input to BBF from 3GPP2

Feature ParameterRange ofValues Write Description

ObjectDefault Reference

Oct 2008 11

Workplan, Process, and Recommendations

Oct 2008 12

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 2008 13

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 2008 14

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 2008 15

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 2008 16

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 2008 17

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