1. Subject:3GPP2 1x Circuit Services Architecture Evolution Principles Date: 25 January 2010 Source: Airvana China Telecom Contact: Doug Knisely, dknisely@airvana.comdknisely@airvana.com Jinlian Wu, wujl@gsta.comwujl@gsta.com Yingqi Li, liyq@chinatelecom.com.cnliyq@chinatelecom.com.cn cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. The contributors grant 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. The contributors are 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 contributors 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 the contributors. The contributors specifically reserve the right to amend or modify the material contained herein and to any intellectual property of the contributors other than provided in the copyright statement above.

2. Phase 2 Objectives Support interface from femtocell subsystem to MSC via A1/A2 or to MSCe via A1p/A2p Timely standardization Functional equivalence between MSC/MSCe-based architecture and MAP/ANSI-41-based architecture Common support for new functional capabilities for Phase 1 and Phase 2 architectures – Enterprise/public spaces – Enhanced handin/handout/SHO/etc. – Complete supplemental services – Etc. 25 January 20102 1x Circuit Services Architecture Evolution Principles

3. Assumptions HRPD architecture changes are independent of 1x circuit architecture changes 1x circuit bearer plane based on RTP/A2/A2p are independent of Phase 2 architecture options Encourage standards-based FAP ecosystem development Maintains TR-069/FMS-based management model Scalability of femtocell subsystem is still paramount 25 January 20103 1x Circuit Services Architecture Evolution Principles

4. 3GPP2 1x Circuit Services High Level Architecture CN Interface: - MAP/ANSI-41 (Phase 1) - MSC/A1 or A1p (Phase 2) Femtocell Subsystem required functionality: - Support 1x-Circuit CN capabilities (e.g., MS authentication, circuit services, SMS, supplemental services) - FAP registration (e.g., providing GW/CSRV with required operational parameters to support mobility, paging, etc.) - UE/MS registration (per 1x session) - Support for handin/handout/paging optimization/etc. - Highly scalable 25 January 20104 1x Circuit Services Architecture Evolution Principles

5. Major Components of the FAP-to- GW/CSRV Interface A1 Application Layer messaging (to 1x circuit CN) – Registration/security – Service access A1 Application Layer encapsulation/ representation FAP control protocols – FAP/UE registration – Mobility/handoff/paging Transport protocol stack over public/private internet Circuit bearer protocol stack (RTP/A2(p), etc.) OA&M protocols 25 January 2010 1x Circuit Services Architecture Evolution Principles 5

6. Abstract GW/CSRV Generic Functional Architecture 25 January 20106 1x Circuit Services Architecture Evolution Principles

7. X.S0059-0 and A.S0024-0 Instantiation (Phase 1, A.S0024-0, X.S0059-0) 25 January 20107 1x Circuit Services Architecture Evolution Principles

8. Phase 2 Alternatives for Major Components A1 Transport Stack – A1p (SCTP/SUA, etc.) – New Protocol (e.g., UDP or TCP-based)? – SIP-encapsulation FAP Control Protocols (same functionality as X.S0059- 200 and A.S0024-0) – Re-use Phase 1 (SIP-based) – New Protocols? FAP Control Protocol Stack – SCTP/SUA-like, etc. – New Protocol (e.g., UDP or TCP-based)? – SIP-encapsulation 25 January 2010 1x Circuit Services Architecture Evolution Principles 8

9. A1(p) CN Instantiation (Phase 2) (A1p-like FAP Interface Option, ~X50-20091207-039) 25 January 20109 1x Circuit Services Architecture Evolution Principles

10. A1(p) CN Instantiation (Phase 2) (SIP-Encapsulated A1 Message Option) 25 January 201010 1x Circuit Services Architecture Evolution Principles

11. Points for Discussion Desirable to build on Phase 1 architecture wherever possible (without compromising Phase 2 objectives) A1 Application Part for FAP-to-GW/CSRV interface should be kept simple – Re-use as much as possible from existing subset of IOS defined in Phase 1 FAP-to-GW/CSRV interface “stack” requires further study – Understand functional/system operator requirements – Single solution/multiple solutions? – Evaluation of re-use/commonality with Phase 1 (service/functional/protocol level) 25 January 201011 1x Circuit Services Architecture Evolution Principles

12. Proposed Short-term Agreements A1/A2 and A1p/A2p interfaces from femtocell subsystem to MSC/MSCe Commonality of the A1 Application Part and call flows at the application layer for the FAP should be common between ANSI-41 (Phase 1) and A1(p) (Phase 2) architectures High priority study items (functional requirements, system operator requirements, and technical comparison of alternatives): – A1 Application Part – FAP control/management protocols – Transport protocol stack (Fxi) 1x Circuit bearer plane agreed to be RTP/A2 at Stage 1/2 level Maintain OA&M (TR-069-based) model (MO extensions may be required for Phase 2 architecture and new capabilities, obviously) 25 January 2010 1x Circuit Services Architecture Evolution Principles 12

13. Proposed Phase 2 Architecture (A1p/MSCe Case) 25 January 201013 1x Circuit Services Architecture Evolution Principles

14. Proposed Phase 2 Architecture (A1/MSC Case) 25 January 201014 1x Circuit Services Architecture Evolution Principles