3GPP2 X.S0059-000-A Version 1.0 Date: December 2011

Femtocell Network: Overview

COPYRIGHT 2011 3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at [email protected]. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information. 3GPP2 X.S0059-000-A v1.0

Revision History

Revision Description of Changes Date Rev. 0 v1.0 Initial Publication January 2010 Rev. A v1.0 Updated Publication December 2011

3GPP2 X.S0059-000-A v1.0

1 cdma2000 Femtocell Network: Overview 2 3 4 5 CONTENTS 6 7 List of Figures ...... iii 8 9 List of Tables...... iv 10 11 Foreword ...... v 12 13 1 Introduction...... 1 14 15 1.1 Scope...... 1 16 17 1.2 Document Conventions...... 1 18 19 2 References...... 2 20 2.1 Normative References...... 2 21 22 3 Definitions and Abbreviations ...... 3 23 24 3.1 Definitions ...... 3 25 26 3.2 Abbreviations...... 3 27 28 4 List of Parts ...... 6 29 30 5 Architectural Model and Reference Points...... 7 31 5.1 Femtocell cdma2000 1x Circuit Service Architecture ...... 7 32 33 5.1.1 IMS-based Femtocell cdma2000 1x Circuit Service Architecture with MSC...... 7 34 5.1.2 IMS-based Femtocell cdma2000 1x Circuit Service Architecture with MSCe ...... 8 35 36 5.1.3 IOS-based Femtocell cdma2000 1x Circuit Service Architecture with MSC...... 8 37 5.1.4 IOS-based Femtocell cdma2000 1x Circuit Service Architecture with MSCe...... 9 38 39 5.1.5 Network Entities...... 10 40 5.1.6 Reference Points...... 11 41 5.1.7 Protocol Descriptions ...... 12 42 43 5.1.7.1 FIAP (Femtocell IOS Application Protocol) 12 44 5.1.7.2 FIAPCP (FIAP Convergence Protocol) 12 45 5.1.7.3 FCP (Femtocell Control Protocol) 12 46 5.1.7.4 FCPCP (FCP Convergence Protocol) 13 47 5.1.7.5 FIAP/FIAPCP Transport Protocols 13 48 49 5.1.7.6 FCP/FCPCP Transport Protocols 13 50 5.1.8 cdma2000 1x Circuit Protocol Stack ...... 14 51 5.1.8.1 IMS-based Femtocell Architecture 14 52 53 5.1.8.2 IOS-based Femtocell Architecture 15 54 5.2 HRPD/cdma2000 1x Packet Data Femtocell Architecture ...... 17 55 56 5.2.1 Network Entities...... 17 57 5.2.2 Reference Points...... 18 58 5.2.3 Protocol Stack...... 19 59

000-i Contents 3GPP2 X.S0059-000-A v1.0

5.2.3.1 Control Plane 19 1 2 5.2.3.2 User Plane 20 3 5.3 eHRPD Femtocell Architecture ...... 20 4 5 5.3.1 Network Entities ...... 21 6 5.3.2 Reference Points ...... 22 7 5.3.3 Protocol Stack...... 22 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

Contents 000-ii 3GPP2 X.S0059-000-A v1.0

1 2 LIST OF FIGURES 3 4 Figure 1 IMS-based cdma2000 1x Circuit Service Femtocell Network Architecture with MSC...... 7 5 6 Figure 2 IMS-based cdma2000 1x Circuit Service Femtocell Network Architecture with 7 MSCe ...... 8 8 Figure 3 IOS-based cdma2000 1x Circuit Service Femtocell Network Architecture with MSC...... 9 9 10 Figure 4 IOS-based cdma2000 1x Circuit Service Femtocell Network Architecture with 11 MSCe ...... 10 12 Figure 5 Control Plane between MS and FCS for Voice/SMS...... 14 13 14 Figure 6 User Plane between MS and MGW for Voice ...... 14 15 16 Figure 7 Control Plane Protocol Stacks when the FGW Uses A1p to the MSCe ...... 15 17 Figure 8 User Plane Protocol Stacks when the FGW Uses A1p to the MSCe...... 15 18 19 Figure 9 Control Plane Protocol Stacks when the FGW Uses A1 to the MSC...... 16 20 Figure 10 User Plane Protocol Stacks when the FGW Uses A1 to the MSC ...... 16 21 22 Figure 11 Protocol Stacks for FCP (FCP and FCP/FCPCP Transport) ...... 16 23 24 Figure 12 HRPD/cdma2000 1x Packet Femtocell Network Architecture ...... 17 25 Figure 13 Control Plane between FAP and SeGW...... 19 26 27 Figure 14 Control Plane Between FAP, FGW, and PDSN...... 19 28 Figure 15 Control Plane Between MS and PDSN ...... 20 29 30 Figure 16 User Plane ...... 20 31 32 Figure 17 eHRPD Femtocell Network Architecture...... 21 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

000-iii List of Figures X.S0059-000-A v1.0

1 2 LIST OF TABLES 3 4 Table 1 List of Parts ...... 6 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

List of Tables 000-iv 3GPP2 X.S0059-000-A v1.0

1 2 FOREWORD 3 4 (This foreword is not part of this specification.) 5 6 7 This document was prepared by the Third Generation Partnership Project 2 (3GPP2) TSG-X 8 Working Group. This document is a new specification. 9 10 This document is part of a multi-part document. The multiple parts together specify the 11 cdma2000®1 Femtocell Network. 12 13 14 This document is subject to change following formal approval procedures. Should this 15 document be modified in the future, it will be re-released with a change-of-release date and an 16 identifying change in version number as follows: 17 18 X.S0059-000-X-n 19 20 where: 21 22 . X: a numerical or uppercase alphabetic character [A, B, C, …] that indicates the 23 revision level; 24 25 . n: a numeric string [1, 2, 3, …] that indicates the point release level. 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 1 cdma2000 is the trademark for the technical nomenclature for certain specifications and standards of the 58 Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000 is a 59 registered trademark of the Industry Association (TIA-USA) in the .

000-v Foreword X.S0059-000-A v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 This page is intentionally left blank. 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

Foreword 000-vi 3GPP2 X.S0059-000-A v1.0

1 2 1 Introduction 3 4 This document provides an overview of the series of documents that specify the HRPD, 5 eHRPD, and cdma2000 1x Femtocell network. 6 7 8 9 1.1 Scope 10 11 This series of documents defines an architecture model and set of specifications for an HRPD, 12 eHRPD, and cdma2000 1x Femtocell network that can support existing services provided by 13 HRPD, eHRPD, and cdma2000 1x. 14 15 16 1.2 Document Conventions 17 18 “Shall” and “shall not” identify requirements to be followed strictly to conform to this 19 document and from which no deviation is permitted. “Should” and “should not” indicate that 20 one of several possibilities is recommended as particularly suitable, without mentioning or 21 excluding others, that a certain course of action is preferred but not necessarily required, or 22 that (in the negative form) a certain possibility or course of action is discouraged but not 23 prohibited. “May” and “need not” indicate a course of action permissible within the limits of 24 25 the document. “Can” and “cannot” are used for statements of possibility and capability, 26 whether material, physical or causal. 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

1 Introduction 000-1 X.S0059-000-A v1.0

1 2 2 References 3 4 5 6 2.1 Normative References 7 8 This section provides references to other specifications and standards that are necessary to 9 implement this document. 10 11 References are either specific (identified by date of publication, revision identifier, and 12 version number) or non-specific. 13 . For a specific reference, subsequent revisions may not apply. 14 15 . For a non-specific reference, the latest revision applies. 16 17 18 [X.S0002] 3GPP2: X.S0002-0 v2.0, “MAP Location Services Enhancements”; 19 June 2006. 20 21 [X.S0024] 3GPP2: X.S0024-0 v1.0, “IP-Based Location Services”; November 2005. 22 [C.S0022] 3GPP2: C.S0022-B v1.0, “Position Determination Service for cdma2000 23 Spread Spectrum Systems”; April 2009. 24 25 [J-STD-036] Joint ATIS/TIA: J-STD-036-C, “Enhanced 9-1-1 Phase II”; 26 January 2009. 27 28 [TS23.002] 3GPP: TS 23.002 v9.1.0, “Network Architecture (Release 9)”; 29 September 2009. 30 31 [X.S0011] 3GPP2: X.S0011-E v1.0, “cdma2000 Wireless IP Network Standard”; 32 November 2009. 33 34 [A.S0024] 3GPP2: A.S0024-A v1.0, “Interoperability Specification (IOS) for 35 Femtocell Access Points”; April, 2011. 36 [A.S0012] 3GPP2: A.S0012-C v3.0, “Interoperability Specification (IOS) for 37 cdma2000 Access Network Interfaces – Part 2 Transport”; 38 39 September 2010. 40 [A.S0014] 3GPP2: A.S0014-C v3.0, “Interoperability Specification (IOS) for 41 cdma2000 Access Network Interfaces – Part 4 (A1, A1p, A2, and A5 42 Interfaces)”; September 2010. 43 44 [A.S0022] 3GPP2: A.S0022-A v1.0, “Interoperability Specification (IOS) for 45 Evolved High Rate Packet Data (eHRPD) Radio Access Network 46 Interfaces and Interworking with Enhanced Universal Terrestrial Radio 47 Access Network (E-UTRAN)”; February 2011. 48 49 [X.S0057] 3GPP2: X.S0057, “E-UTRAN – eHRPD Connectivity and Interworking: 50 Core Network Aspects”. 51 52 [X.S0059-100] 3GPP2: X.S0059-100-A, “cdma2000 Femtocell Network: Packet Data 53 Network Aspects”. 54 55 [X.S0059-200] 3GPP2: X.S0059-200-A, “cdma2000 Femtocell Network: 1x and IMS 56 Network Aspects”. 57 58 [X.S0059-400] 3GPP2: X.S0059-400-0, “cdma2000 Femtocell Network: Overview”. 59

000-2 2 References 3GPP2 X.S0059-000-A v1.0

1 2 3 Definitions and Abbreviations 3 4 This section provides definitions, symbols and abbreviations that are used throughout the 5 document. 6 7 8 9 3.1 Definitions 10 11 For the purposes of this document, the following definitions apply. 12 13 Femtocell Access Point (FAP) 14 15 A Femtocell Access Point (FAP) provides cdma2000 coverage in a small area, usually a 16 private residence or a small office, and connects the MS to an operator’s network via a 17 IP connection (e.g., DSL, cable). The FAP may operate in cdma2000 1x mode, 18 HRPD mode, eHRPD mode, or any combination thereof. The FAP, when operating in 19 eHRPD mode, is referred to as an eFAP. 20 21 22 Femtocell Access Control 23 This function allows any MS that is part of the Access Control List (ACL) for a FAP to access 24 services through that FAP. The types of Femtocell access control include open association, 25 restricted association, and signaling association. 26 27 28 Open Association 29 30 Any MS can register with the FAP and access the services provided by cdma2000 1x, HRPD, 31 and eHRPD. 32 33 Restricted Association 34 35 Only an MS in the ACL for a given FAP is allowed to register and access the services 36 provided by cdma2000 1x, HRPD, and eHRPD. 37 38 Signaling Association 39 40 Any MS can register with the FAP, but during a service access, the MS may be redirected to a 41 macro if that MS is not included in the FAP ACL (i.e., the MS is not authorized 42 to access service through the FAP). 43 44 45 46 3.2 Abbreviations 47 48 3GPP2 3rd Generation Partnership Project 2 49 AAA Authentication, Authorization and Accounting 50 51 AC Authentication Center 52 ACL Access Control List 53 ACS Auto-Configuration Server 54 55 AKA Authentication and Key Agreement 56 AN Access Network 57 58 BS Base Station 59 BSC Base Station Controller

3 Definitions and Abbreviations 000-3 X.S0059-000-A v1.0

1 DSL 2 3 eAN Evolved Access Network 4 eFAP Evolved Femtocell Access Point 5 6 eHRPD Evolved High Rate Packet Data 7 EPC Evolved Packet Core 8 FA Foreign Agent 9 10 FAP Femtocell Access Point 11 FCP Femtocell Control Protocol 12 13 FCPCP Femtocell Control Protocol Convergence Protocol 14 FCS Femtocell Convergence Server 15 FIAP Femtocell IOS Application Protocol 16 17 FMS Femtocell Management System 18 HA Home Agent 19 20 HLR Home Location Register 21 HRPD High Rate Packet Data 22 HSGW HRPD Serving Gateway 23 24 IKE Key Exchange 25 IMS IP Multimedia Subsystem 26 27 IOS Interoperability Specification 28 IP Internet Protocol 29 IPsec IP Security 30 31 ISC IP Multimedia Service Control 32 L1 Layer 1 33 34 L2 Layer 2 35 L3 Layer 3 36 37 LAC Link Access Control 38 LIIWF LMSD-IMS Interworking Function 39 LIPA Local IP Access 40 41 LMA Local Mobility Anchor 42 LMSD Legacy MS Domain 43 44 MAC Media Access Control 45 MAG Mobile Access Gateway 46 MAP Mobile Application Part 47 48 MC Message Center 49 MGCF Media Gateway Control Function 50 51 MGW Media Gateway 52 MIP Mobile IP 53 MS Mobile Station 54 55 MSC Mobile Switching Center 56 PCF Packet Control Function 57 58 PCRF Policy and Charging Rules Function 59 PMIP Proxy Mobile IP

000-4 3 Definitions and Abbreviations 3GPP2 X.S0059-000-A v1.0

1 PDSN Packet Data Service 2 3 PDST Packet Data Service Termination 4 PSAP Public Safety Answering Point 5 6 QoS 7 SCTP Stream Control Transmission Protocol 8 TCAP Transaction Capabilities Application Part 9 10 RIPA Remote IP Access 11 RPC Remote Procedure Call 12 13 RTP Real-Time Transport Protocol 14 SeGW Security Gateway 15 SIP Session Initiation Protocol 16 17 SMS Short Message Service 18 TCP Transmission Control Protocol 19 20 UA User Agent 21 UDP User Datagram Protocol 22 URL Uniform Resource Locator 23 24 VoIP Voice over IP 25 WAN 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

3 Definitions and Abbreviations 000-5 X.S0059-000-A v1.0

1 2 4 List of Parts 3 4 The Parts that comprise of this document are shown in Table 1. Each document in the series 5 is numbered as a Part. Each Part represents an area of focus within the series of documents. 6 7 8 Table 1 List of Parts 9 Part Title 10 11 000-A cdma2000 Femtocell Network: Overview 12 13 100-A cdma2000 Femtocell Network: Packet Data Network Aspects 14 200-A cdma2000 Femtocell Network: 1x and IMS Network Aspects 15 16 400-0 cdma2000 Femtocell Network: 1x Supplementary Service Aspects 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

000-6 4 List of Parts 3GPP2 X.S0059-000-A v1.0

1 2 5 Architectural Model and Reference Points 3 4 5 6 5.1 Femtocell cdma2000 1x Circuit Service Architecture 7 8 This section describes cdma2000 1x circuit service Femtocell network architectures. 9 10 11 5.1.1 IMS-based Femtocell cdma2000 1x Circuit Service Architecture with 12 MSC 13 14 The figure below shows the access network reference architecture for cdma2000 1x circuit 15 service access from a Femtocell base station. This figure represents the IMS-based 16 architecture used with an MSC. 17 18 PDE MPC 19 20 21 22 HLR/AC MC 23 MAP 24 25 26 FCS 27 28 ISUP 1x Macro A1 PSTN PSAP 29 Base MSC A2 TDM 30 Station 31 TDM 32 TDM ISUP 33 ISUP 34 MGCF Ma (SIP), /MGW ISC (SIP), 35 or Sh 36 (Diameter) Fx1 (RTP) 37 Mg (SIP) Femtocell 38 Fx3 Access Point Fx1 (RTP) 39 IP Fx2 (SIP) 40 1x SIP Security IMS MS Network 41 UA Gateway Fx2 (SIP) 42

43 A12 (AAA) Fx4 (AAA) Fm Fx1 (RTP) Mm (SIP) 44 Legend: FMS 45 AN- IP Multimedia FCS Femtocell Convergence Server F-AAA 46 Network FMS Femtocell Management System AAA 47 F-AAA Femtocell AAA 48 49 Figure 1 IMS-based cdma2000 1x Circuit Service Femtocell Network Architecture with MSC 50 51 Notes: 52 1. Location Based Services are supported using [X.S0002], [X.S0024], and [C.S0022]. 53 Emergency services calls are supported using [J-STD-036]. 54 55 2. The Ma, Mg, Mm, Sh and ISC reference points are as defined in [TS23.002]. 56 57 58 59

5 Architectural Model and Reference Points 000-7 X.S0059-000-A v1.0

1 5.1.2 IMS-based Femtocell cdma2000 1x Circuit Service Architecture with 2 3 MSCe 4 5 The figure below shows the access network reference architecture for cdma2000 1x circuit 6 service access from a Femtocell base station. This figure represents the IMS-based 7 architecture used with an MSCe in support of LMSD. 8 9 10 PDE MPC 11 12 13

HLR/AC MC 14 MAP 15 MAP 16 17 18 LMSD/ FCS 19 zz (LMSD SIP) IMS IWF 20 1x Macro A1p 21 Base MSCe 13 (ISUP) 22 Station PSTN 34 (TDM) 23 39 (H.248) 24 MGW Mm (SIP) Ma (SIP), A2p ISC (SIP), or 25 TDM ISUP Sh 26 (Diameter) PSAP 27 MGCF 28 Mg (SIP) /MGW 29 Fx1 (RTP) Femtocell IMS 30 Fx3 Access Point Fx1 (RTP) 31 IP Fx2 (SIP) 32 1x SIP Security MS Network 33 UA Gateway Fx2 (SIP) 34 Mm (SIP) 35 A12 Fm Fx1 (RTP) Fx4 (AAA) 36 (AAA) Legend: FMS 37 AN- IP Multimedia FCS Femtocell Convergence Server F-AAA 38 AAA Network FMS Femtocell Management System 39 F-AAA Femtocell AAA 40 Figure 2 IMS-based cdma2000 1x Circuit Service Femtocell Network Architecture with MSCe 41 42 Notes: 43 44 1. The LMSD-IMS Interworking Function (LIIWF) provides interworking between the 45 MSCe [X.S0025] and IMS by interworking LMSD SIP and IMS SIP. This function 46 is outside of the scope of this document. 47 48 2. The Ma, Mg, Mm, Sh and ISC reference points are as defined in [TS23.002]. 49 50 5.1.3 IOS-based Femtocell cdma2000 1x Circuit Service Architecture with 51 52 MSC 53 54 The figure below shows the access network reference architecture for cdma2000 1x circuit 55 service access from a Femtocell base station. This figure represents the IOS-based 56 architecture used with an MSC. 57 58 59

000-8 5 Architectural Model and Reference Points 3GPP2 X.S0059-000-A v1.0

1

2

3 PDE MPC 4 5

6 HLR/AC MC 7 MAP 8 9 10 11 12 ISUP 13 1x Macro A1 PSTN PSAP Base MSC TDM 14 Station A2 15 A1 16 17 A2 18 19 20 MGW 21 Femtocell 22 Access Point Fx3 E 23 A2p (RTP) 24 Fx6 FGW/ 1x Security FAP FLCS 25 MS Gateway A25 (Opt) 26 27 Fm 28 Legend: A12 (AAA) Fx4 (AAA) 29 FGW Femtocell Gateway FMS FLCS Femtocell Legacy Convergence Server AN- 30 F-AAA FMS Femtocell Management System AAA 31 F-AAA Femtocell AAA 32 33 34 Figure 3 IOS-based cdma2000 1x Circuit Service Femtocell Network Architecture with MSC 35 36 Notes: 37 1. Location Based Services are supported using [X.S0002], [X.S0024], and [C.S0022]. 38 Emergency services calls are supported using [J-STD-036]. 39 40 2. Either A1/A2 interface to MSC or E interface to the MAP network is used. 41 42 3. The interface between the MGW and FGW is outside the scope of this document. 43 44 5.1.4 IOS-based Femtocell cdma2000 1x Circuit Service Architecture with 45 46 MSCe 47 The figure below shows the access network reference architecture for cdma2000 1x circuit 48 49 service access from a Femtocell base station. This figure represents the IOS-based 50 architecture used with an MSCe. 51 52 53 54 55 56 57 58 59

5 Architectural Model and Reference Points 000-9 X.S0059-000-A v1.0

1 2 3 PDE MPC 4 5 6 HLR/AC MC 7 MAP MAP 8 9 10 11 12 13 1x Macro A1p 14 Base MSCe 13 (ISUP) Station 15 PSTN 16 17 39 (H.248) 18 A2p A1p 19 PSAP 20 MGW 21 22 Femtocell Access Point 23 Fx3 A2p (RTP) 24 Fx6 FGW/ E 25 1x Security MS FAP FLCS Gateway A25 (Opt) 26 27 28 A12 Fx4 (AAA) Fm Legend: (AAA) 29 FMS FGW Femtocell Gateway 30 AN- FLCS Femtocell Legacy Convergence Server F-AAA 31 FMS Femtocell Management System AAA 32 F-AAA Femtocell AAA 33 Figure 4 IOS-based cdma2000 1x Circuit Service Femtocell Network Architecture with MSCe 34 35 Notes: 36 37 1. Location Based Services are supported using [X.S0002], [X.S0024], and [C.S0022]. 38 Emergency services calls are supported using [J-STD-036]. 39 2. Either A1p/A2p interface or E interface to the MAP network is used. 40 41 3. The A2p interface between the FAP and MGW may go directly between the FAP 42 and the MGW without going through the FGW. 43 44 45 5.1.5 Network Entities 46 47 This document defines the following network entities: 48 49 . Femtocell Access Point (FAP); 50 . Security Gateway (SeGW); 51 52 . Femtocell AAA; 53 54 . Femtocell Management System (FMS); 55 56 . Access Network AAA (AN-AAA); 57 58 . Femtocell Convergence Server (FCS); and 59

000-10 5 Architectural Model and Reference Points 3GPP2 X.S0059-000-A v1.0

1 . Femtocell Gateway (FGW). 2 3 4 Femtocell Access Point 5 6 The FAP provides access for cdma2000 1x MS devices to support cdma2000 1x circuit 7 services. This entity also provides a Femtocell access control function. 8 9 Security Gateway 10 11 The Security Gateway (SeGW) provides security functions for FAP access to the cdma2000 12 core network. It supports: secure tunnel management procedures between itself and the FAP, 13 including establishment and release of the tunnel; allocation of an IP address to the FAP from 14 the serving cdma2000 network; and encapsulation and de-capsulation of packets to and from 15 the FAP. Through the interface to the Femtocell AAA, the SeGW supports Femtocell level 16 authentication and transfer of authorization policy information. 17 18 19 Femtocell AAA 20 The Femtocell AAA provides a FAP authorization function. It sends authorization policy 21 information to the SeGW. 22 23 24 Femtocell Convergence Server 25 The Femtocell Convergence Server (FCS) is an IMS Application Server that provides 26 27 interworking among: the FAP that is supporting the cdma2000 1x mobile; the SIP 28 environment of IMS; and the appropriate MAP network elements (e.g., HLR, MC, MPC, 29 cdma2000 1x MSC). 30 31 AN-AAA 32 33 The AN-AAA provides authorization function for Femtocell access control. 34 35 Femtocell Gateway/Femtocell Legacy Convergence Server 36 37 The Femtocell Gateway (FGW) is a network entity that resides in an operator’s network and 38 provides gateway convergence functions between either an MSC (over the A1/A2 IOS 39 interfaces), an MSCe (over the A1p/A2p IOS interfaces), or the MAP network (over the E 40 interface) and the FAP (over the Fx6 interface). The FGW provides aggregation, proxy, and 41 signal routing functions for the FAPs to access services within the system operator’s core 42 network. 43 44 45 Femtocell Management System 46 47 The Femtocell Management System (FMS) is a network entity that resides in an operator's 48 network and aids in the auto-configuration of the FAP before the MS can access services 49 through the FAP. 50 51 5.1.6 Reference Points 52 53 The following reference points are introduced: 54 55 Fx1 The RTP bearer interface between the FAP and the Media Gateway (MGW) that 56 carries the RTP payloads. 57 58 Fx2 The signaling interface that carries user SIP signaling between the FAP and the 59 IMS core network.

5 Architectural Model and Reference Points 000-11 X.S0059-000-A v1.0

1 Fx3 The IPsec tunnel between the FAP and the SeGW. 2 3 Fx4 The signaling interface between the Security Gateway and the Femtocell AAA. 4 5 Fx6 The signaling interface that carries application layer protocols on behalf of the 6 MS between the FAP and the FGW. 7 8 A25 The signaling interface that carries control protocols between the FAP and the 9 FGW. A25 is optional and is used only when SIP is not being used to provide 10 transport of Fx6. 11 12 Fm The interface between the FAP and the FMS for auto-configuration. 13 14 5.1.7 Protocol Descriptions 15 16 The protocol stacks for the Femtocell 1x control plane provide six general functions: 17 18 1. Femtocell IOS Application Protocol (FIAP) – conveys 1x circuit core network 19 related information elements using a subset of IOS Application Layer messages; 20 21 2. FIAP Convergence Protocol (FIAPCP) -- representation and encapsulation of the 22 FIAP messages; 23 24 3. Femtocell Control Protocol (FCP) – control protocol between the FGW and the FAP 25 to provide Femtocell-specific control functions (e.g., FAP registration, MS binding 26 for MSs that are being served by the FAP, paging control and optimization); 27 4. FCP Convergence Protocol (FCPCP) – representation and encapsulation of the FCP 28 messages; 29 30 5. FIAP/FIAPCP transport protocols; and 31 32 6. FCP/FCPCP transport protocols. 33 34 35 5.1.7.1 FIAP (Femtocell IOS Application Protocol) 36 The FIAP is comprised of a subset of IOS Application Layer messages (as defined in 37 [A.S0014] and [A.S0024]) that are used between: 38 39 . the FAP and the FGW, or 40 41 . the FAP and the FCS, when SIP/IMS are used with an FCS (see Section 5.1.1. and 42 5.1.2). 43 44 45 5.1.7.2 FIAPCP (FIAP Convergence Protocol) 46 There are two optional protocols for FIAPCP: 47 48 1. The A1 application layer message encapsulation and representation protocol as 49 defined in [X.S0059-200]. This encapsulation and representation protocol is used 50 when the FIAP messages are transported using SIP. 51 52 2. SUA as defined in [A.S0012]. This encapsulation and representation protocol is 53 used when the FIAP messages are transported using the A1p SCTP protocol stack. 54 55 56 5.1.7.3 FCP (Femtocell Control Protocol) 57 58 There are two optional protocols for FCP: 59

000-12 5 Architectural Model and Reference Points 3GPP2 X.S0059-000-A v1.0

1 1. SIP – SIP is used to transport FIAP messages to provide FAP registration, MS 2 binding (for MSs that are being served by the FAP), paging control and optimization 3 functions, etc., according to [X.S0059] and [A.S0024]. In this case, basic SIP 4 procedures (e.g., SIP Registration) are used along with a minimal set of extensions 5 (e.g., carried with SIP MESSAGE or SIP INFO requests). 6 7 2. A25 – A25 is used when FIAP messages are transported using the protocol stack as 8 specified in [A.S0024] to provide FAP registration, MS binding (for MSs that are 9 being served by the FAP), paging control and optimization functions, etc. A25 is 10 optional and is not used when SIP is being used to transport FIAP messages. 11 12 13 5.1.7.4 FCPCP (FCP Convergence Protocol) 14 15 There are two optional protocols for FCPCP: 16 17 1. SIP with Femtocell-specific extensions as defined in [X.S0059] and [A.S0024]. 18 2. A25 representation as defined in [A.S0024]. FCPCP is assumed to be null in this 19 case. 20 21 22 5.1.7.5 FIAP/FIAPCP Transport Protocols 23 24 There are two optional protocol stacks for FIAP/FIAPCP transport: 25 26 1. SIP transported over TCP, UDP, or SCTP according to [X.S0059] and [A.S0024]. 27 2. SCTP/IP. 28 29 30 5.1.7.6 FCP/FCPCP Transport Protocols 31 32 There are two optional protocol stacks for FCP/FCPCP transport: 33 34 1. SIP transported over TCP, UDP, or SCTP according to [X.S0059] and [A.S0024] 35 when SIP is being used to transport FIAP messages. 36 2. SCTP when A25 is being used as the FCP. 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

5 Architectural Model and Reference Points 000-13 X.S0059-000-A v1.0

1 5.1.8 cdma2000 1x Circuit Protocol Stack 2 3 4 5.1.8.1 IMS-based Femtocell Architecture 5 6 7 5.1.8.1.1 Control Plane between MS and FCS for Voice/SMS 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Figure 5 Control Plane between MS and FCS for Voice/SMS 25 26 27 28 29 5.1.8.1.2 User Plane between MS and MGW for Voice 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 Figure 6 User Plane between MS and MGW for Voice 47 48 49 50 51 52 53 54 55 56 57 58 59

000-14 5 Architectural Model and Reference Points 3GPP2 X.S0059-000-A v1.0

1 5.1.8.2 IOS-based Femtocell Architecture 2 3 4 5.1.8.2.1 Control Plane Protocol Stacks when the FGW Uses A1p to the MSCe 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

20 21 Figure 7 Control Plane Protocol Stacks when the FGW Uses A1p to the MSCe 22 23 24 25 5.1.8.2.2 User Plane Protocol Stacks when the FGW Uses A1p to the MSCe 26 27 28 29 30 RTP RTP 31 Voice Voice 32 UDP UDP 33 IP/IPsec IP/IPsec IP IP IP 34 CDMA2000 CDMA2000 35 air air 36 L1/L2 L1/L2 L1/L2 L1/L2 L1/L2 37 38 MS FAP SeGW FGW/FLCS MGW 39 40 Figure 8 User Plane Protocol Stacks when the FGW Uses A1p to the MSCe 41 42 Note: FGW is optional in the bearer plane for RTP traffic. 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

5 Architectural Model and Reference Points 000-15 X.S0059-000-A v1.0

1 5.1.8.2.3 Control Plane Protocol Stacks when the FGW Uses A1 to the MSC 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Figure 9 Control Plane Protocol Stacks when the FGW Uses A1 to the MSC 19 20 21 22 23 5.1.8.2.4 User Plane Protocol Stacks when the FGW Uses A1 to the MSC 24 25 26 27 28 29 30 31 32 33 34 35 36 Figure 10 User Plane Protocol Stacks when the FGW Uses A1 to the MSC 37 38 39 40 41 5.1.8.2.5 Protocol Stacks for FCP (FCP and FCP/FCPCP Transport) 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 Figure 11 Protocol Stacks for FCP (FCP and FCP/FCPCP Transport)

000-16 5 Architectural Model and Reference Points 3GPP2 X.S0059-000-A v1.0

1 2 5.2 HRPD/cdma2000 1x Packet Data Femtocell Architecture 3 4 The following figures show the HRPD or cdma2000 1x Packet Data Femtocell network 5 architecture. 6 7 In these figures, the only new interfaces introduced (see [X.S0011] and [TS23.002]) are: the 8 interface between Femtocell Access Point and Security Gateway; the interface between 9 Femtocell Access Point and Femtocell Management System; the interface between the 10 Security Gateway and Femtocell AAA; and the interface between the Security Gateway and 11 AAA. 12 13 14 The HRPD Femtocell network architecture also supports Local IP Access (LIPA) which 15 allows an MS to access either local IP networks or the internet through the local interface. 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 Figure 12 HRPD/cdma2000 1x Packet Femtocell Network Architecture 46 47 Note: All interfaces that pass through the SeGW entity are transported within a secure tunnel 48 between the FAP and the SeGW. The Fx3 interface between FAP and SeGW is not shown in 49 the figure. 50 51 52 5.2.1 Network Entities 53 54 A description of new network entities and entities with new functions is provided below. 55 56 Femtocell Access Point 57 58 The FAP provides access for cdma2000 1x and HRPD devices to support cdma2000 1x 59 packet data and HRPD services. This entity also provides a Femtocell access control function.

5 Architectural Model and Reference Points 000-17 X.S0059-000-A v1.0

1 Security Gateway 2 3 The Security Gateway (SeGW) is a network entity that resides in an operator's network and 4 provides secure access for the Femtocell Access Point to access services within the system 5 operator’s network. 6 7 8 Femtocell Gateway 9 The Femtocell Gateway (FGW) is a network entity that resides in an operator's network and 10 provides aggregation and proxy functions for the Femtocell Access Point to access services 11 within the system operator’s network. 12 13 14 Femtocell AAA 15 16 The Femtocell AAA provides a FAP authorization function. It sends authorization policy 17 information to the SeGW. 18 19 Femtocell Management System 20 21 The Femtocell Management System (FMS) is a network entity that resides in an operator's 22 network and aids in the auto-configuration of the FAP before the MS can access services 23 through the FAP. 24 25 26 AN-AAA 27 In addition to the function described in [C.S0022] and [J-STD-036], the AN-AAA also 28 provides a Femtocell access control function and LIPA authorization function. For LIPA 29 authorization, the AN-AAA may access the Home AAA for authorization information, but 30 this interface is outside the scope of this Specification. 31 32 33 5.2.2 Reference Points 34 35 The following new reference points make use of existing protocols and interfaces that are 36 specified by 3GPP2 TSG-A, TSG-X, and IETF: 37 38 . A12 for HRPD access authentication between the AN function in the FAP and the 39 AN-AAA. 40 41 . A13 for HRPD idle session handoff between the AN function in the FAP and another 42 HRPD AN (AN). Identical to the HRPD A13 interface between two ANs. 43 . A16-19 for HRPD active session handoff between the AN function in the FAP and 44 45 another HRPD AN. Identical to the HRPD A16-19 interface(s) between two ANs. 46 . A10/A11 interface between the AN/PCF function in the FAP and the PDSN. 47 48 . MIP/Proxy MIP between the FA/MAG function in the FGW and the HA/LMA. 49 50 51 The architecture contains the following new reference points: 52 Femtocell Access Point – Security Gateway (Fx3) 53 54 The interface provides IPsec tunnel between Femtocell Access Point and Security Gateway. 55 56 57 Security Gateway – Femtocell AAA (Fx4) 58 The interface provides authorization to the Femtocell Access Point. 59

000-18 5 Architectural Model and Reference Points 3GPP2 X.S0059-000-A v1.0

1 Femtocell Access Point – Femtocell Management System (Fm) 2 3 The Fm interface enables auto-configuration of the FAP by the FMS. 4 5 6 SeGW – AAA (Fx5) 7 The Fx5 interface enables the AAA to authorize the MS for Remote IP Access (RIPA) to the 8 FAP. 9 10 11 5.2.3 Protocol Stack 12 13 14 5.2.3.1 Control Plane 15 16 5.2.3.1.1 Control Plane between FAP and SeGW 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 Figure 13 Control Plane between FAP and SeGW 35 36 37 38 5.2.3.1.2 Control Plane Between FAP, FGW, and PDSN 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 Figure 14 Control Plane Between FAP, FGW, and PDSN 54 55 56 57 58 59

5 Architectural Model and Reference Points 000-19 X.S0059-000-A v1.0

1 5.2.3.1.3 Control Plane Between MS and PDSN 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Figure 15 Control Plane Between MS and PDSN 20 21 22 23 5.2.3.2 User Plane 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

43 Figure 16 User Plane 44 45 46 47 5.3 eHRPD Femtocell Architecture 48 49 The following figure shows the eHRPD Femtocell network architecture. The architecture 50 shown in Figure 20 does not support optimized handoff between E-UTRA and eHRPD. 51 52 53 54 55 56 57 58 59

000-20 5 Architectural Model and Reference Points 3GPP2 X.S0059-000-A v1.0

1 The eHRPD Femtocell network architecture also supports Local IP Access (LIPA) and remote 2 IP Address (RIPA) as defined in section 5.2 of this document. 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 Figure 17 eHRPD Femtocell Network Architecture 42 43 44 5.3.1 Network Entities 45 46 Refer to section 5.2.1, [A.S0022], and [X.S0057] for description of network entities, except 47 for the following. 48 49 Evolved Femtocell Access Point (eFAP) 50 51 The eFAP is a cdma2000 that provides coverage in a small area, usually 52 a private residence or a small office, and connects the UE to the EPC (Evolved Packet core) 53 of an operator’s network via a broadband connection (e.g., DSL, cable). This entity also 54 provides a Femtocell access control function. 55 56 57 58 59

5 Architectural Model and Reference Points 000-21 X.S0059-000-A v1.0

1 5.3.2 Reference Points 2 3 Refer to section 5.2.2 of this document and [X.S0057] for description of reference points with 4 the exception PDSN is replaced with HSGW. 5 6 7 5.3.3 Protocol Stack 8 9 Refer to section 5.2.3 of this document for description of protocol stack with the exception 10 PDSN is replaced with HSGW. 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

000-22 5 Architectural Model and Reference Points