3GPP2 A.S0024-A v1.0 April 2011 Interoperability Specification (IOS) for Femtocell Access Points

Transcription

1 GPP A.S00-A v.0 April 0 Interoperability Specification (IOS) for Femtocell Access Points 0, GPP GPP 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 GPP Secretariat at secretariat@gpp.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See for more information.

2 Revision History Date Revision Description January 00 A.S00-0 v.0 Initial revision. For features supported, refer to section. April 0 A.S00-A v.0 Includes support for IOS-based x architecture, x Femtocell Access Control, out-of-band indication enhancements for x active handoff from a macro BS to a FAP and dormant handoff from a macro AN to a FAP. LIPA requirements and call flows (now addressed in X.S00) are removed.

3 GPP A.S00-A v.0 Table of Contents Foreword... xii Introduction Overview Purpose Scope Document Convention References Normative References Informative References Terminology Acronyms Definitions Architecture Femtocell SIP-Based x Voice Architecture Femtocell SIP-based x RAN Network Entities Femtocell SIP-based x RAN Interfaces Femtocell IOS-based x Voice Architecture Femtocell x IOS-based RAN Network Entities Femtocell x IOS-based RAN Interfaces Protocol Stack Femtocell x and HRPD Packet Data Femtocell x and HRPD RAN Packet Data Network Entities Femtocell x and HRPD RAN Packet Data Interfaces Femtocell ehrpd Packet Data Femtocell ehrpd RAN Packet Data Network Entities Femtocell ehrpd RAN Packet Data Interfaces HRPD LIPA IOS Femtocell Assumptions Feature Descriptions Explicitly Supported Features FAP Power-up x Dormant Handoff Between the Macro BS and the FAP x Active Handoff Between the Macro BS and the FAP HRPD Dormant Handoff Between the Macro AN/PCF and the FAP... - i

4 GPP A.S00-A v Connected State Session Transfer Between the FAP and the Macro AN Femtocell Access Control x OOB Indication of MS Detection... - Requirements and Procedures Femtocell Requirements SIP-based x RAN Femtocell Requirements IOS-based x RAN Femtocell Requirements IOS Signaling Routing Cell ID Aggregation UZID Aggregation Transport Layer Requirements Use of SUA for Ap Use of SCCP for A x Packet Data and HRPD Femtocell Requirements Security Association for x and HRPD Packet Data Femtocells x Packet Data Support ehrpd Femtocell Operation Femtocell Access Control Femtocell Access Control Authorization and Enforcement Points Access Control List x Femtocell Access Control AN-AAA as x Authorization Point HRPD Femtocell Access Control AN-AAA as HRPD FAC Authorization Point LIPA Requirements and Procedures... - Femtocell Interfaces FGW and RAN Interfaces SIP-based FAP to Core Network Interface A Formatted Messages Used on Fx Measurement Procedures Measurement Request Successful Operation Failure Operation Measurement Response Successful Operation Failure Operation... - ii

5 GPP A.S00-A v Femtocell Supplementary Info Successful FCS Operation Successful FAP Operation Failure Operation MS OOB Indication Successful Operation Failure Operation FAP RAN Interfaces A/Ap and A/Ap Interfaces A0/A Interface A Interface A RADIUS Attribute Definition Femtocell-Access-Control-Authorization HRPD Access Authentication and x Access Authorization A Interface HRPD Dormant Handoff from FAP to Macro AN/PCF A Interface Connected-State Handoff from FAP to a Macro AN Connected-State Handoff from Macro AN to a FAP A (IP Tunneling) Interface A Interface A Interface Network/Transport Protocol Specification Use of the SUA for A Use of SCTP A Interface Message Procedures A-FAP Registration Request Successful Operation Failure Operation A-FAP Registration Response Successful Operation Failure Operation A-FAP Deregistration Successful Operation Failure Operation A-Measurement Request Successful Operation... - iii

6 GPP A.S00-A v Failure Operation A-Measurement Response Successful Operation Failure Operation A-MS OOB Indication Successful Operation A-Femtocell Supplementary Info Successful FAP Operation Failure FAP Operation None.Successful FGW Operation Failure FGW Operation A Interface A Interface Network/Transport Protocol Specification A Interface Message Procedures A-FAP Registration Request Successful Operation Failure Operation A-FAP Registration Response Successful Operation Failure Operation A-FAP Deregistration Successful Operation Failure Operation A-Measurement Request Successful Operation Failure Operation A-Measurement Response Successful Operation Failure Operation... - FAP Call Flows FAP Operation FAP Power-up IOS-based x FAP Registration/Deregistration x FAP Registration x FAP Deregistration FAP-initiated FAP Deregistration... - iv

7 GPP A.S00-A v FGW-initiated FAP Deregistration HRPD FAP Registration/Deregistration HRPD FAP Registration HRPD FAP Deregistration FAP-initiated HRPD FAP Deregistration FGW-initiated HRPD FAP Deregistration SIP-based x RAN Call Flows MS/AT Power-up at the FAP MS Registration and Paging at the FAP SIP-based x Handoff SIP-based x Macro BS to FAP Dormant Handoff (Intra-PDSN) SIP-based x Macro BS to FAP Dormant Handoff (Inter-PDSN) SIP-based x FAP to Macro BS Dormant Handoff SIP-based x Macro BS to FAP Active Handoff SIP-based x Macro BS to FAP Active Handoff Measurements x Macro BS to FAP Active Handoff with Early OOB Link Detection x Macro BS to FAP Active Handoff with Late OOB Link Detection MS OOB Indication SIP-based x FAP to Macro BS Active Handoff IOS-based x RAN Call Flows MS Registration Mobile Origination Mobile Termination IOS-based x Handoff Macro BS to FAP Dormant Handoff (Intra-PDSN) Macro BS to FAP Dormant Handoff (Inter-PDSN) FAP to Macro BS Dormant Handoff Macro BS to FAP Active Handoff Macro BS to FAP Active Handoff Measurements Macro BS to FAP Active Handoff with Early OOB Link Detection Macro BS to FAP Active Handoff with Late OOB Link Detection A-MS OOB Indication FAP to Macro BS Active Handoff Inter-FAP Active Handoff Active Optimized Inter-FAP Handoff with Ap Active Optimized Inter-FAP Handoff with A... - v

8 GPP A.S00-A v HRPD Call Flows HRPD Handoff HRPD Macro AN/PCF to FAP Dormant Handoff HRPD FAP to Macro AN/PCF Dormant Handoff HRPD Macro AN/PCF to FAP Connected State Session Transfer HRPD FAP to Macro AN/PCF Connected State Session Transfer LIPA Session Establishment between FAP and AT... - Messages, Information Elements and Timer Definitions Message Definitions A and Ap Message Definitions Measurement Request Measurement Response Femtocell Supplementary Info MS OOB Indication A Message Definition A-FAP Registration Request A-FAP Registration Response A-FAP Deregistration A-Measurement Request A-Measurement Response A-MS OOB Indication A-Femtocell Supplementary Info A Message Definitions A-FAP Registration Request A-FAP Registration Response A-FAP Deregistration A-Measurement Request A-Measurement Response Information Element Definitions A and Ap Information Element Definitions A and Ap Information Element Identifiers Message Type Long Code Cause Measurement Response Options Measurement Report... - vi

9 GPP A.S00-A v Global RAND Key Pilot List Nonce Mobile Identity OOB Indication A Information Element Definitions A Information Element Identifiers A Cross Reference of IEs with Messages A Message Type FAP Identifier x Cell Info Reg/Dereg Cause Cell Identifier List Classmark Information Type Downlink Radio Environment CDMA Serving One Way Delay MS Measured Channel Identity IS-000 Channel Identity Long Code Measurement Response Options Mobile Identity Measurement Report Cause OOB Indication Global RAND Key Authentication Response Parameter Nonce A Information Element Definitions A Information Element Identifiers A Cross Reference of IEs with Messages A Message Type FAP Identifier Sector Info AT-ID Long Code Mask Measurement Response Options... - vii

10 GPP A.S00-A v.0... Measurement Report Cause Timer Definitions Timer Descriptions T mr T mr T regreq viii

11 GPP A.S00-A v.0 Table of Figures Figure..- Femtocell SIP-based xvoice Architecture with MSC... - Figure..- Femtocell SIP-based x Voice Architecture with MSCe... - Figure..- Femtocell IOS-based x Voice Architecture with Ap/Ap Interfaces... - Figure..- Femtocell IOS-based x Voice Architecture with A/A Interfaces... - Figure...- Femtocell x IOS-Based Protocol Reference Model-Control Plane... - Figure...- Femtocell x IOS-Based Protocol Reference Model- User Plane... - Figure...- Femtocell x IOS-Based Protocol Reference Model-Control Plane... - Figure...- Femtocell x IOS-Based Protocol Reference Model- User Plane... - Figure..- Femtocell x Packet Data Architecture Figure..- Femtocell HRPD Packet Data Architecture Figure..- Femtocell ehrpd Packet Data Architecture... - Figure...- DRN/SRN and Source/Destination Address Usage Between FAP and FGW... - Figure...- DRN/SRN and Source/Destination Address Usage Between FGW and MSCe... - Figure...- SLR/DLR and SPC/DPC Usage Between FGW and MSC... - Figure...- GPP RADIUS Attribute Format... - Figure..- FAP Power-up... - Figure...- FAP Registration... - Figure...- FAP-initiated FAP Deregistration... - Figure...- FGW-initiated FAP Deregistration... - Figure...- FAP Registration... - Figure...- FAP-initiated HRPD FAP Deregistration... - Figure...- FGW-initiated HRPD FAP Deregistration... - Figure...- x Macro BS to FAP Dormant Handoff (Intra-PDSN)... - Figure...- x Macro BS to FAP Dormant Handoff (Inter-PDSN)... - Figure...- x Macro BS to FAP Active Handoff... - Figure...- x Macro BS to FAP Active Handoff with Early OOB Link Detection Figure...- x Macro BS to FAP Active Handoff with Late OOB Link Detection... - Figure...- MS OOB Indication... - Figure...- x FAP to Macro BS Active Handoff... - Figure..- Mobile Registration via a Circuit Switched MSC/MSCe... - Figure..- Mobile Origination via a Circuit Switched MSC... - Figure..- Mobile Termination via a Circuit Switched MSC... - Figure...- x Macro BS to FAP Active Handoff Figure...- x Macro BS to FAP Active Handoff with Early OOB Link Detection... - ix

12 GPP A.S00-A v.0 Figure...- x Macro BS to FAP Active Handoff with Late OOB Link Detection... - Figure...- A-MS OOB Indication... - Figure...- Active Optimized Inter-FAP Handoff, FGW with Ap... - Figure...- Active Optimized Inter-FAP Handoff, FGW with A... - Figure...- HRPD FAP to Macro AN/PCF Dormant Handoff... - Figure...- HRPD Macro AN/PCF to FAP Active Handoff... - x

13 GPP A.S00-A v.0 Table of Tables 0 Table...- Use of SUA for FCP Messages... - Table...- BSMAP Messages... - Table...- Cause Class Values... - Table...- Cause Values... - Table...0- Mobile Identity - Type of Identity Coding... - Table...0- Mobile Identity - Type of OOB Identity Coding Table...- A Cross Reference of IEs with Messages... - Table...- Cross Reference of IEs with Messages... - Table..- Timer Values and Ranges Sorted by Name... - xi

14 GPP A.S00-A v.0 Foreword The foreword is not part of this standard. This document describes the protocols and procedures to support Femtocell Access Points (FAPs) in the Radio Access Network (RAN). xii

15 GPP A.S00-A v Introduction This document contains the procedures, call flows and message descriptions associated with Femtocell Access Point (FAP) support in the access network.. Overview This document includes a description of the interface protocols and procedures to support the following features and functions. Features and functions explicitly supported in this specification: Femtocell power-up x dormant handoff between the macro BS and the FAP x active handoff between the macro BS and the FAP High Rate Packet Data (HRPD) dormant handoff between the macro AN and the FAP HRPD connected state session transfer between the FAP and the macro AN x and HRPD Femtocell Access Control (FAC) including x authorization at the AN-AAA x out-of-band (OOB) indication that an MS is or is not detected in the proximity of a Femtocell. Note: Local IP Access (LIPA) is specified in X.S00-00 []. The features and functions that are explicitly not supported in this specification are: Soft handoff between Femtocells Concurrent packet and circuit voice service.. Purpose The purpose of this document is to provide a standard and call flows for the Femtocell interfaces within the Radio Access Network (RAN)... Scope This document provides an interoperability specification for a RAN that supports Femtocell operation. This document contains message procedures and formats necessary to obtain this interoperability... Document Convention Shall and shall not identify requirements to be followed strictly to conform to the standard and from which no deviation is permitted. Should and should not indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others; that a certain course of action is preferred but not necessarily required; or (in the negative form) that a certain possibility or course of action is discouraged but not prohibited. May and need not indicate a course of action permissible within the limits of the standard. Can and cannot are used for statements of possibility and capability, whether material, physical, or causal.. References References are either normative or informative. A normative reference is used to include another document as a mandatory part of a GPP specification. Documents that provide additional non-essential information are included in the informative references section. -

16 GPP A.S00-A v Normative References The following standards contain provisions which, through reference in this text, constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based upon this document are encouraged to investigate the possibility of applying the most recent editions published by them. [] GPP: A.S000-C v.0, Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network, June, 00. [] GPP: A.S000-C v.0, Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Packet Control Function, June 00. [] GPP: A.S00-D v.0, Interoperability Specification (IOS) for cdma000 Access Network Interfaces - Part Transport, September 00. [] GPP: A.S00-D v.0, Interoperability Specification (IOS) for cdma000 Access Network Interfaces - Part Features, September 00. [] GPP: A.S00-D v.0, Interoperability Specification (IOS) for cdma000 Access Network Interfaces Part (A, Ap, A, and A Interfaces), September 00. [] GPP: A.S00-D v.0, Interoperability Specification (IOS) for cdma000 Access Network Interfaces Part (A0 and A Interfaces), September 00. [] GPP: A.S00-A v.0, Interoperability Specification (IOS) for Evolved High Rate Packet Data (ehrpd) Radio Access Network Interfaces and Interworking with Enhanced Universal Terrestrial Radio Access Network (E-UTRAN), February 0. [] GPP: C.S000-E v.0, Upper Layer (Layer ) Signaling Standard for cdma000 Spread Spectrum Systems, June 00. [] GPP: C.S00-B v.0, cdma000 High Rate Packet Data Air Interface Specification, September 00. [0] GPP: C.S00-0 v.0, E-UTRAN - cdma000 Connectivity and Interworking: Air Interface Specification, January, 00. [] GPP: S.S0-0 v.0, Femtocell Security Framework, December 00. [] GPP: X.S000-E v.0, Mobile Application Part (MAP), April 00. [] GPP: X.S00-D v.0, Wireless IP Network Standard, November 00. [] GPP: X.S00-0 v.0, E-UTRAN - ehrpd Connectivity and Interworking: Core Network Aspects, September 00. [] GPP: X.S A v.0, cdma000 Femtocell Network Overview. [] GPP: X.S00-00-A v.0, cdma000 Femtocell Network Packet Data Network Aspects. [] GPP: X.S00-00-A v.0, cdma000 Femtocell Network: x and IMS Network Aspects. Editor s Note: The above documents ([], [] and []) are works in progress and should not be referenced unless and until they are approved and published. Until such time as this Editor s Note is removed, the inclusion of the above documents is for informational purposes only. [] IETF: RFC, User Datagram Protocol, August 0. [] IETF: RFC, Remote Authentication Dial In User Service (RADIUS), June

17 GPP A.S00-A v.0 0 [0] IETF: RFC, Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS), July Informative References [I-] GPP: X.R00-0 v.0, GPP Femtocell Configuration Parameters. [I-] GPP: S.R000-B v.0, Network Reference Model for CDMA000 Spread Spectrum Systems, May 00. [I-] GPP: S.R00-B v.0 IP Network Architecture Model for cdma000 Spread Spectrum Systems, June 00. [I-] [I-] Terminology.. Acronyms GPP rd Generation Partnership Project ACL AN AAA AN-AAA AT BS BSMAP CDMA CHAP CVSE DNS ESN Access Control List Access Network Authentication, Authorization and Accounting Access Network Authentication, Authorization and Accounting Access Terminal Base Station Base Station Mobile Application Part Code Division Multiple Access Challenge Handshake Authentication Protocol Critical Vendor Specific Extension Domain Name System Electronic Serial Number FAC Femtocell Access Control FACDIR Facilities Directive FAP Femtocell Access Point FCP Femtocell Control Protocol FCS Femtocell Convergence Server FEID Femtocell Equipment Identifier FGW FIAP FMS HRPD IE Femtocell Gateway Femtocell IOS Application Protocol Femtocell Management System High Rate Packet Data Information Element -

18 GPP A.S00-A v.0 IMS IMSI IOS IP kbps LIPA MEID MGW MS MSC MSCe NVSE OOB PCF PCM PDSN PLCM PPP PSMM RADIUS RAN RFC RTP SC/MM SCTP SeGW SIP SUA UATI UDP VSA VoIP IP Multimedia Subsystem International Mobile Subscriber Identity Interoperability Specification Internet Protocol kilobit per second Local IP Access Mobile Equipment Identity Media Gateway Mobile Station Mobile Switching Center Mobile Switching Center Emulation Normal Vendor Specific Extension out-of-band Packet Control Function Pulse Code Modulation Packet Data Serving Node Public Long Code Mask Point to Point Protocol Pilot Strength Measurement Message Remote Authentication Dial-In User Service Radio Access Network Request for Comments Real-time Transport Protocol Session Control / Mobility Management Stream Control Transmission Protocol Security Gateway Session Initiation Protocol Signaling Connection Control Part User Adaptation Layer Unicast Access Terminal Identifier User Datagram Protocol Vendor Specific Attribute Voice over IP.. Definitions out-of-band A Formatted Message A communication means other than a cdma000 x or HRPD air interface. An A message defined in this document that is transported on the Fx interface or an A/Ap message that is transported on the A interface. cdma000 is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of GPP. Geographically (and as of the date of publication), cdma000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. -

19 GPP A.S00-A v.0. Architecture x and HRPD Femtocell IOS messaging and call flows are based on the architecture reference models shown in this section. In the figures, solid lines indicate signaling and bearer and dashed lines indicate only signaling... Femtocell SIP-Based x Voice Architecture Figure..- and Figure..- show the RAN reference architecture for SIP-based x voice access from a FAP. For voice, the x signaling and user plane packets are converted at the FAP to Session Initiation Protocol (SIP) and Voice over IP (VoIP) traffic respectively. MS x x FAP IPsec tunnel (Fx) SeGW A Fm Core Network Fx Fx IMS AN-AAA FMS MGCF/ MGW FCS Macro BS A A MSC MAP 0 Figure..- Femtocell SIP-based xvoice Architecture with MSC MS x x FAP IPsec tunnel (Fx) SeGW A Fm Core Network Fx Fx IMS AN-AAA FMS MGCF/ MGW FCS Macro BS Ap Ap MSCe Figure..- Femtocell SIP-based x Voice Architecture with MSCe MAP... Femtocell SIP-based x RAN Network Entities The entities identified in Figure..- and Figure..- are defined as follows. BS The macro base station (BS) is an entity in the public radio telecommunications system used for radio telecommunications with MSs. -

20 GPP A.S00-A v FAP The Femtocell Access Point (FAP) is a wireless access point operating in licensed spectrum to connect a mobile station (MS) to the operator s network through the public Internet infrastructure. In x, this entity enables access to x voice users by providing a conversion function between x voice and IP Multimedia Subsystem (IMS)-based VoIP traffic and signaling. MS The mobile station (MS) is an entity in the public cellular radio telecommunications service intended to be used while in motion or during halts at unspecified points. MSC/MSCe The Mobile Switching Center (MSC) may be either a circuit-switched MSC or an IP based MSCe (emulation) and provides processing and control for calls and services. Refer to S.R000 [I-] for MSC and S.R00 [I-] for MSCe. SeGW The Security Gateway (SeGW) is an entity residing in an operator s network that provides for secure access for the FAP to network operator services. Refer to X.S []. AN-AAA The AN Authentication, Authorization and Accounting server may perform access control authorization for the x FAP. Core network entities are specified in X.S [].... Femtocell SIP-based x RAN Interfaces The interfaces identified in Figure..- and Figure..- are defined as follows. x For details on the air interface, refer to C.S000 []. A This interface carries signaling information between the mobility management functions of the circuit-switched MSC and the call control component of the macro BS. Ap This interface carries signaling information between the mobility management functions of the MSCe and the call control component of the macro BS. A This interface is used to provide a path for user traffic. The A interface carries / kbps PCM information (for circuit-oriented voice) or kbps Unrestricted Digital Information (UDI, for ISDN) between the circuit-switched MSC and the BS. Ap This interface provides a path for packet-based user traffic sessions. The Ap interface carries bearer information via IP packets between the Media Gateway (MGW) and the BS. A The A interface carries signaling information related to access authentication and Femtocell Access Control authorization between the FAP and the AN Authentication, Authorization and Accounting (AN-AAA) entity. Fx For details on the bearer interface between the FAP and the MGW, refer to X.S []. Fx For details on the signaling interface between the FAP and the IMS, refer to X.S []. Fx For details on the IPsec tunnel between the FAP and the SeGW refer to X.S []. Fm The Fm interface enables auto-configuration of the FAP by the FMS. Refer to X.R00 [I-] and X.S []... Femtocell IOS-based x Voice Architecture Figure..- and Figure..- show the RAN reference architecture for IOS-based x access from a FAP with the support of the Ap/Ap and the A/A interfaces, respectively. -

21 GPP A.S00-A v.0 MS x x FAP IPsec tunnel (Fx) SeGW Fm Ap Ap A A FMS FGW AN-AAA Macro BS Ap MGW Ap Ap MSCe Ap Figure..- Femtocell IOS-based x Voice Architecture with Ap/Ap Interfaces MS x x FAP IPsec tunnel (Fx) SeGW Fm Ap A Ap A FMS FGW AN-AAA MGW A A Macro BS A A MSC 0 0 Figure..- Femtocell IOS-based x Voice Architecture with A/A Interfaces... Femtocell x IOS-based RAN Network Entities The entities identified in Figure..- and Figure..- are defined as follows. AN-AAA The AN Authentication, Authorization and Accounting server may perform access control authorization for the x FAP. BS The macro base station (BS) is an entity in the public radio telecommunications system used for radio telecommunications with an MS. The macro BS connects to an MSC via the A and A interfaces. The macro BS connects to an MSCe and MGW via the Ap and Ap interfaces. FAP The Femtocell Access Point (FAP) is a wireless access point operating in licensed spectrum to connect a mobile station (MS) to the operator s network through the public Internet infrastructure. FGW The Femtocell Gateway (FGW) provides aggregation, proxy, conversion and routing functions for a FAP to access services within an operator s network FMS The Femtocell Management System (FMS) is a network entity residing in an operator's network that aids in FAP auto-configuration before the FAP can provide services. MGW The Media GateWay (MGW) provides an interface between the packet environment of the Core Network and the circuit switched environment of the PSTN for bearer traffic, when equipped with circuit capabilities. The MGW provides vocoding and/or transcoding functions to the bearer traffic if the FGW connects to an MSC. The signaling interface -

22 GPP A.S00-A v.0 MS MSC/MSCe SeGW between the FGW and the MGW is to be specified in a future revision of this specification. The mobile station (MS) is an entity in the public cellular radio telecommunications service intended to be used while in motion or during halts at unspecified points. The Mobile Switching Center (MSC) may be either a circuit-switched MSC or an IP based MSCe (emulation) and provides processing and control for calls and services. The Femtocell Security Gateway (SeGW) provides for secure access for the FAP to network operator services. Refer to X.S [] Femtocell x IOS-based RAN Interfaces The interfaces identified in Figure..- and Figure..- are defined as follows. x For details on the air interface, refer to C.S000 []. A This interface carries signaling information between the mobility management functions of the circuit-switched MSC and the call control component of the FGW/macro BSC. Refer to A.S00 []. Ap This interface carries signaling information between the mobility management functions of the MSCe and the call control component of the macro BS. It also carries signaling information between the mobility management functions of the MSCe and call control component of the FGW, and between the FGW and the FAP. Refer to A.S00 []. A This interface is used to provide a path for user traffic. The A interface carries / kbps PCM information (for circuit-oriented voice) or kbps Unrestricted Digital Information (UDI, for ISDN) between the circuit-switched MSC and the FGW/macro BS. Ap This interface provides a path for packet-based user traffic sessions. The Ap interface carries voice information via IP packets between the Media Gateway (MGW) and the FAP/macro BS. A The A interface carries signaling information related to access authentication and Femtocell Access Control authorization between the FAP and the AN-AAA entity. A This interface carries signaling information between the FAP and the FGW for FAP registration with the FGW and macro x BS active handoff to the FAP. Fx For the details on the IPsec tunnel between the FAP and the SeGW refer to X.S []. Fm The Fm interface enables auto-configuration of the FAP by the FMS. Refer to X.R00 [I-] and X.S []. -

23 GPP A.S00-A v.0... Protocol Stack The Femtocell x IOS-based protocol stack for the Ap/Ap interface is depicted as follows. L Signaling L Signaling IOS (Ap+A) IOS (Ap+A) IOS (Ap) IOS (Ap) LAC LAC SUA SCTP SUA SCTP SUA SCTP SUA SCTP MAC MAC IP/IPSec IP/IPsec IP IP IP IP L L L L L L Phy Phy L L L L L L MS Figure...- FAP SeGW FGW MSCe Femtocell x IOS-Based Protocol Reference Model-Control Plane Voice Voice RTP UDP RTP UDP CDMA000 air CDMA000 air IP/IPsec L/L IP/IPsec L/L IP L/L IP L/L IP L/L MS FAP SeGW FGW MGW Figure...- Femtocell x IOS-Based Protocol Reference Model- User Plane The Femtocell x IOS-based protocol stack for the A/A interface is depicted as follows. L Signaling L Signaling IOS (Ap+A) IOS (Ap+A) IOS (A) IOS (A) LAC LAC SUA SCTP SUA SCTP SCCP SCCP MAC MAC IP/IPSec L IP/IPsec L IP L IP L MTP MTP Phy Phy L L L L L L MS Figure...- FAP SeGW FGW MSC Femtocell x IOS-Based Protocol Reference Model-Control Plane Voice Voice RTP UDP RTP UDP PCM PCM CDMA000 air CDMA000 air IP/IPsec L/L IP/IPsec L/L IP L/L IP L/L L L 0 MS FAP SeGW FGW MSC Figure...- Femtocell x IOS-Based Protocol Reference Model- User Plane -

24 GPP A.S00-A v.0.. Femtocell x and HRPD Packet Data Figure..- shows the reference architecture for x packet data access from a FAP. Figure..- shows the reference architecture for HRPD packet data access from a FAP. IPsec tunnel Fm SeGW MS x x FAP A0 A A FGW FMS Macro x BS/ PCF A0 A AN-AAA Figure..- Femtocell x Packet Data Architecture PDSN AT HRPD HRPD FAP IPsec tunnel A A0 A A A A A Fm SeGW FGW PDSN FMS AN-AAA A Macro HRPD AN/PCF A0 A 0 0 Figure..- Femtocell HRPD Packet Data Architecture... Femtocell x and HRPD RAN Packet Data Network Entities The entities identified in Figure..- and Figure..- are defined as follows. AN The Access Network is a logical entity in the HRPD RAN used for radio communications with the AT. AN-AAA The AN Authentication, Authorization and Accounting server performs access authentication, Femtocell Access Control (FAC) authorization and Local IP Access (LIPA) authorization functions for the RAN. AT The Access Terminal (AT) is a device providing data connectivity to a user. BS The macro base station is an entity in the public radio telecommunications system used for radio telecommunications with MSs. FAP The Femtocell Access Point (FAP) is a wireless access point operating in licensed spectrum to connect an AT to the operator s network through the public Internet infrastructure. FGW The Femtocell Gateway (FGW) is an entity residing in an operator s network that provides aggregation, proxy and registration functions for the FAP to access network operator services. A0, A, A, A, A and A interfaces may pass transparently through the FGW. -0

25 GPP A.S00-A v.0 0 FMS MS PCF PDSN SeGW The Femtocell Management System (FMS) is a network entity residing in an operator's network that aids in FAP auto-configuration before the FAP can provide services. The mobile station is an entity in the public cellular radio telecommunications service intended to be used while in motion or during halts at unspecified points. The Packet Control Function (PCF) is an entity in the RAN that manages the relay of packets between the BS or AN and the PDSN. The Packet Data Serving Node (PDSN) is an entity that routes MS/AT originated or MS/AT terminated packet data traffic. A PDSN establishes, maintains and terminates link layer sessions to MS/ATs. The Security Gateway (SeGW) is a network entity residing in an operator's network that provides secure access for the FAP to the operator s network. Refer to X.S [] Femtocell x and HRPD RAN Packet Data Interfaces The interfaces identified in Figure..- and Figure..- are defined as follows. x For details on the air interface, refer to C.S000 []. A0 This interface carries user traffic between the FAP and the PDSN or between the PCF and the PDSN. A This interface carries signaling information between the FAP and the PDSN or between the PCF and the PDSN. A This interface carries signaling information related to access authentication between the FAP or the AN/PCF and the AN-AAA. This interface may also be used for FAC authorization (refer to section...). A This interface carries signaling information between the Session Control / Mobility Management (SC/MM) function in the macro AN/PCF and the SC/MM function in the FAP for idle state session transfer and inter-an paging when the AT is in idle state. A This interface carries signaling information between the macro AN and the FAP for HRPD inter-an connected state session transfer (hard handoff). A This interface carries buffered user data between the macro AN/PCF and the FAP for an AT, during A session transfer. A This interface carries signaling information between the FAP and the FGW for FAP registration with the FGW and macro AN active handoff to the FAP. Fm The Fm interface enables auto-configuration of the FAP by the FMS. Refer to X.R00 [I-] and X.S []. HRPD For details on the air interface, refer to C.S00 []. -

26 GPP A.S00-A v.0.. Femtocell ehrpd Packet Data Figure..- shows the reference architecture for ehrpd packet data access from an efap. eat ehrpd ehrpd efap IPsec tunnel A A0 A A A A A Fm SeGW FGW HSGW FMS AN-AAA A Macro ean/ epcf A0 A Figure..- Femtocell ehrpd Packet Data Architecture... Femtocell ehrpd RAN Packet Data Network Entities The entities identified in Figure..- are defined as follows. AN-AAA The AN Authentication, Authorization and Accounting server performs access authentication, FAC authorization and LIPA authorization functions for the RAN. ean The Evolved Access Network (ean) is a logical entity in the ehrpd RAN used for radio communications with the eat. eat The Evolved Access Terminal (eat) is a device providing data connectivity to a user. efap The Evolved Femtocell Access Point (efap) is a wireless access point operating in licensed spectrum to connect an eat to the operator s network through the public Internet infrastructure. epcf The Evolved Packet Control Function (epcf) is an entity in the RAN that manages the relay of packets between the ean and the HSGW. FGW The Femtocell Gateway (FGW) is an entity residing in an operator s network that provides aggregation, proxy and registration functions for the efap to access network operator services. FMS The Femtocell Management System (FMS) is a network entity residing in an operator's network that aids in efap auto-configuration before the efap can provide services. HSGW The HRPD Serving Gateway (HSGW) is an entity that routes eat originated or eat terminated packet data traffic. An HSGW establishes, maintains and terminates link layer sessions to eats. SeGW The Security Gateway (SeGW) is a network entity residing in an operator's network that provides secure access for the efap to the operator s network. Refer to X.S [].... Femtocell ehrpd RAN Packet Data Interfaces The interfaces identified in Figure..- are defined as follows. A0 This interface carries user traffic between the efap and the HSGW or between the epcf and the HSGW. -

27 GPP A.S00-A v A This interface carries signaling information between the efap and the HSGW or between the epcf and the HSGW. A This interface carries signaling information related to access authentication between the efap or the ean/epcf and the AN-AAA. This interface may also be used for FAC authorization (refer to section...). A This interface carries signaling information between the Session Control/Mobility Management (SC/MM) function in the macro ean/epcf and the SC/MM function in the efap for idle state session transfer and inter-ean paging when the eat is in idle state. A This interface carries signaling information between the macro ean and the efap for ehrpd inter-ean connected state session transfer (hard handoff). A This interface carries buffered user data between the macro ean/epcf and the efap for an eat, during A session transfer. A This interface carries signaling information between the efap and the FGW for efap registration with the FGW and macro ean active handoff to the efap. Fm The Fm interface enables auto-configuration of the efap by the FMS. Refer to X.R00 [I-] and X.S []. ehrpd For details on the air interface, refer to C.S00 [0]... HRPD LIPA HRPD Local IP Access is specified in X.S00-00 []. IOS Femtocell Assumptions The following assumptions apply to this document.. The SIP-based x voice FAP contains a SIP client that converts x signaling and user plane packets to/from SIP signaling and RTP traffic, respectively.. The IOS-based x voice FAP functions as a x base station subsystem and provides Ap-based Femtocell IOS Application Protocol (FIAP), Ap, and A interfaces to the FGW. Refer to X.S [] for a description of FIAP.. The IOS-based x FGW functions as a BSC and provides the A/A or Ap/Ap interface to the MSC/MSCe or MGW.. Each FAP connects to one and only one SeGW at a time.. Each FAP connects to one and only one FMS at a time.. Each SIP-based x voice FAP is assigned a Cell_ID of type 0H (refer to A.S00 []). The MSC_ID of the Cell_ID corresponds to the Femtocell Convergence Server (FCS) with which the FAP communicates. Refer to X.S00-00 [].. The x packet data/hrpd FAP contains PCF functionality.. Each FAP communicates with the core network entities in the operator s network through the SeGW.. The PN offset broadcast by the x or HRPD FAP may not be unique; it is possible for multiple FAPs within the coverage area of a single macro BS/AN to have the same PN offset. 0. An AN-AAA acting as an enforcement point requires FEID support in the FAP. -

28 GPP A.S00-A v Feature Descriptions This section describes the features identified in the overview in section.... Explicitly Supported Features... FAP Power-up This feature supports FAP power-up and initialization, including neighborhood discovery, network discovery and configuration.... x Dormant Handoff Between the Macro BS and the FAP This feature supports handoff of an idle MS between the macro BS and the FAP.... x Active Handoff Between the Macro BS and the FAP This feature supports handoff of an active MS between the macro BS and the FAP.... HRPD Dormant Handoff Between the Macro AN/PCF and the FAP This feature supports handoff of an idle AT between the macro AN/PCF and the FAP.... Connected State Session Transfer Between the FAP and the Macro AN This feature supports handoff of an active AT between the FAP and the macro AN.... Femtocell Access Control This feature allows a FAP to be able to control which MS/AT can register or receive services from the FAP. A FAP can be configured to have one of the following types of access association. Open Access : any MS/AT can access and receive services from the FAP. However, LIPA service may be further controlled by the AN-AAA. Refer to X.S00-00 []. Signaling Access: any MS/AT can access and register with the FAP, i.e., the MS/AT is reachable/pageable. However, the MS/AT that is not on the access control list (ACL) may be redirected to a macro BS or AN when it attempts to establish a traffic connection. Restricted Access: only an MS/AT that is on the ACL is allowed to access or register. The FAP does not complete the registration process of any MS/AT that is not on the access control list. This specification explicitly supports the FAP being an enforcement point for a x MS or HRPD AT where the ACL is provided by the FMS. This specification also explicitly supports the AN-AAA being an enforcement point for the HRPD FAP. This specification transparently supports other core network entities being enforcement points for both x and HRPD. Note that emergency services (e.g., global emergency call) may be exempt from Femtocell access control, based on operator policy.... x OOB Indication of MS Detection This feature allows a FAP that can detect, via out-of-band (OOB) mechanism, an authorized MS in its proximity to indicate this detection to the FGW or FCS, to disambiguate the target FAP during active hand-in. Open, Signaling and Restricted Access may also be referred to as Open, Signaling and Restricted Association. -

29 GPP A.S00-A v Requirements and Procedures This section describes the requirements and procedures associated with this specification.. Femtocell Requirements This section describes the requirements associated with this specification... SIP-based x RAN Femtocell Requirements The requirements for a SIP-based x RAN Femtocell are specified in X.S00-00 []... IOS-based x RAN Femtocell Requirements... IOS Signaling Routing The number of cells that the MSC/MSCe supports may be limited. In this case, multiple FAPs can share the same cell ID under the MSC/MSCe. The FGW shall maintain a mobility context for each MS attached to a FAP, and uses the mobility context to route downlink IOS signaling from the MSC/MSCe to the appropriate FAP. When the FGW receives the first Complete Layer Information message from an MS via the FAP, the FGW shall send the Complete Layer Information message to the MSC/MSCe and set up the mobility context including the MS s identity and the FAP s identity, if the MS registers with the MSC/MSCe successfully. Otherwise, the FGW shall clear the mobility context entry for the MS. The FGW shall maintain the mobility context when a mobility event occurs. When a connectionless downlink IOS signaling message (e.g., a Paging Request or ADDS Page message) is received by the FGW, the FGW determines the target FAP based on the mobility context. Connection oriented IOS signaling messages are routed over the SUA/SCCP signaling connection identified by the Source/Destination Reference Number or the Local Reference Number. If the FGW detects an underlying transport layer failure between the FAP and the FGW, the FGW shall send a Clear Request message for each active MS associated with the corresponding FAP to the MSC/MSCe and start an instance of timer T 00 to wait for each corresponding Clear Command message from the MSC/MSCe. Upon receiving each Clear Command message from the MSC/MSCe the FGW shall stop timer T 00 and send a Clear Complete message to the MSC/MSCe. The FGW also clears the mobility context of the MS. The FAP should release the call for the MS when the FAP detects the transport layer failure to the FGW. When the FGW receives a Handoff Request message from the MSC/MSCe, the FGW may determine the target FAP based on the A measurement procedure (refer to section...), and route the Handoff Request message to the target FAP. When the handoff procedure successfully occurs, the FGW establishes the mobility context for the MS. When the FGW can not identify the target FAP, the FGW shall send a Handoff Failure message to the MSC/MSCe. When the FGW receives a Handoff Required message from the FAP and the FGW determines that the target cell is a FAP under control of the same FGW then the FGW sends a Handoff Request message to the target FAP. If the FGW determines that the target cell is not a FAP under control of the same FGW, then the FGW sends a Handoff Required message to the MSC/MSCe.... Cell ID Aggregation The FGW is identified to the MSC/MSCe using one or more unique Cell IDs. The number of FAPs supported by an FGW may exceed the number of available Cell ID values, and in this case the Cell ID -

30 GPP A.S00-A v value used in Ap messages sent between the FGW and the supported FAPs are not unique. The FGW is responsible for correlating the unique Cell ID used by the MSC/MSCe to the potentially non-unique Cell ID used by the FAPs, together with internal knowledge of FAP registration information, signaling tunnel endpoints, etc. Also refer to section UZID Aggregation The FGW may map the UZID coming from the FAP to a user zone sent to the MSC/MSCe on the A/Ap interface. This mapping is not specified in this document.... Transport Layer Requirements For SUA and SCCP protocol descriptions, refer to A.S00 []. For the first signaling connection initiated by the FAP, FAP shall set the DRN value to zero. For the first signaling connection initiated by the FGW, FGW shall set the DRN value to zero. Both the FAP and the FGW shall maintain the mapping info between DRN and SRN to identify the signaling connection between the FAP and the FGW. For the first signaling connection initiated by the FGW, FGW shall set the DLR value to zero. For the first signaling connection initiated by the MSC, MSC shall set the DLR value to zero. Both the FGW and the MSC shall maintain the mapping info between DLR and SLR to identify the signaling connection between the FGW and the MSC.... Use of SUA for Ap The SUA protocol is used between FAP and FGW, and between FGW and MSCe. The SUA Source/Destination Reference Number (SRN/DRN) is a four-byte element internally chosen by the MSCe, FGW or FAP to uniquely identify a signaling connection between the FAP and the FGW, or between the FGW and the MSCe. Referring to Figure...-, in the FAP to FGW direction, the SRN is chosen by the FAP. The Source Address is set to the FAP s IP address assigned by the SeGW and the Destination Address is set to the FGW s IP address. In the FGW to FAP direction, the SRN is chosen by the FGW. The Source Address is set to the FGW s IP address and the Destination Address is set to the FAP s IP address. In the FGW to FAP direction, the FGW echoes the FAP SRN in the DRN field. In the FAP to FGW direction, the FAP echoes the FGW SRN in the DRN field. Note that it is the responsibility of the FAP and the FGW to ensure that no two calls have identical SUA local reference numbers. FAP DRN (FGW), SRN (FAP) Src addr (FAP), Dst addr (FGW) DRN (FAP), SRN (FGW) Src addr (FGW), Dst addr (FAP) FGW 0 Figure...- SRN: Source Reference Number DRN: Destination Reference Number DRN/SRN and Source/Destination Address Usage Between FAP and FGW Referring to Figure...-, in the FGW to MSCe direction, the SRN is chosen by the FGW. The Source Address is set to the FGW s IP address and the Destination address is set to the MSCe s IP address. In the MSCe to FGW direction, the SRN is chosen by the MSCe. The Source Address is set to the MSCe s IP address and the Destination address is set to the FGW s IP address. In the MSCe to FGW direction, the MSCe echoes the FGW SRN in the DRN field. In the FGW to MSCe direction, the FGW echoes the MSCe SRN in the DRN field. Note that it is the responsibility of the FGW and the MSCe to ensure that no two calls have identical SUA local reference numbers. -

31 GPP A.S00-A v.0 FGW DRN (MSCe), SRN (FGW) Src addr (FGW), Dst addr (MSCe) DRN (FGW), SRN (MSCe) Src addr (MSCe), Dst addr (FGW) MSCe Figure...- SRN: Source Reference Number DRN: Destination Reference Number DRN/SRN and Source/Destination Address Usage Between FGW and MSCe 0... Use of SCCP for A The SCCP protocol is used between the FGW and the MSC. The SCCP Source/Destination Local Reference (SLR/DLR) number is a three-byte element internally chosen by the MSC or the FGW to uniquely identify a signaling connection. Referring to Figure...-, in the FGW to MSC direction, the SLR is chosen by the FGW. The Source Point Code (SPC) is set to the FGW s signaling point code and the Destination Point Code (DPC) is set to the MSC s signaling point code. In the MSC to FGW direction, the SLR is chosen by the MSC. The SPC is set to the MSC s point code and the DPC is set to the FGW s point code. In the MSC to FGW direction, the MSC echoes the FGW SLR in the DLR field. In the FGW to MSC direction, the FGW echoes the MSC SLR in the DLR field. Note that it is the responsibility of the FGW and the MSC to ensure that no two calls have identical SCCP local reference numbers. FGW DLR (MSC), SLR (FGW) SPC (FGW), DPC (MSC) DLR(FGW), SLR(MSC) SPC(MSC), DPC(FGW) MSC Figure...- SLR/DLR: Source/Destination Local Reference SPC/DPC: Source/Destination Point Code SLR/DLR and SPC/DPC Usage Between FGW and MSC 0.. x Packet Data and HRPD Femtocell Requirements... Security Association for x and HRPD Packet Data Femtocells The x or HRPD packet data FAP shall maintain a security context for the PDSN to which it is attached. This context consists of an authentication algorithm and mode, a secret (shared key or appropriate public/private key pair), and a style of replay protection in use. This context is used to populate the Mobile-Home Authentication Extension and Registration Update Authentication Extension Information Elements (IEs). Refer to A.S00 [] for more information. 0. x Packet Data Support Upon receiving a x Origination or x Enhanced Origination Message from the MS with the service option set to 0xH (i.e., SO ), the FAP may acknowledge the message from the MS as described in C.S000 []. If the FAP acknowledges the x origination and the MS is already x registered via the FAP, the FAP shall establish or perform service option negotiation procedures over the traffic channel (to support SO ) with the MS directly and follow the BS procedures specified in A.S00 [] for setup of the A0 with the PDSN. Otherwise, if the MS is not registered via the FAP, the FAP shall perform the MS registration procedures as specified in X.S00-00 [] or section.. and after successful registration, establish the traffic channel (to support SO ) with the MS directly and follow the BS procedures in A.S00 [] for setup of the A0 with the PDSN. -