3GPP2 Femto Architecture Summary (January â€“July 2008)

1

3GPP2 Femto Architecture Summary

(January – July 2008)

09/26/2008

James Ni

2

Overview

� Summarizes all Femto Architectures proposed to 3GPP2

• January 2008 Hollywood meeting

• February 2008 Xiamen meeting

• April 2008 Montreal meeting

• May 2008 Osaka meeting

• June 2008 Cancun meeting

• July 2008 Orlando meeting

� 3GPP2 targeted date for femto architecture baseline document

• Q4 2008

� Two major camps

• Pro SIP/IMS camp

• Pro legacy protocol tunneling camp

3

January 08 Hollywood meeting

summary

4

January 08 Hollywood meeting summary

� Formally started working on Femto architecture

� Proposed femto architecture baseline

� Call for member contributions

5

January 08 Hollywood meeting summary

6

February 08 Xiamen meeting

summary

7

February 08 Xiamen meeting summary

� Received a number of architecture proposals from members

� Two focuses:

• 1x voice accessing architecture

• Data accessing architecture

8

Proposed Architectures (Qualcomm)

� Qualcomm proposed 5 different architectures

• 2 architectures for supporting 1x circuit-switched services

– SIP/IMS based architecture

– A1p/A2p/MSCe based architecture

• 3 architectures for supporting HRPD and 1x packet-switched services

– Split PDSN architecture

– PDSN in macro architecture

– PDSN in femto architecture

� Qualcomm did not show any preference to any one of the proposed

architectures

9

Proposed Architectures (Qualcomm 1)

� SIP/IMS based architecture

10


� ANSI-41 based Handoff

• Via SIP / ANSi-41 Interworking AS and legacy MSC

� A21 Handoff

• Via VCC (Voice Call Continuity) AS

Femto-Macro Handoff

Security gateway to macro network

• IPsec tunnels with femto cell

Femto Security Gateway Function

SIP/ANSI-41 Interworking ASWhere Call is Anchored

Provided by SIP/ANSI-41 Interworking AS1x Supplementary Services

� SIP: For 1x call and service signaling with IMS Core

� RTP: For voice and user traffic transport

Interface to Macro Network

Macro Core Network Support

Femto Cell Components

� IMS / SIP servers deployment

� SIP/ANSI-41 Interworking Application Server (AS)

* Convert between SIP and ANSI-41

• Interfaces with 1x HLR, MSC

* MSC/VLR functions

• Authentication with 1x HLR

• Location Management

• Call control

• Handoff management

• Supplementary services

BTS, BSC, SIP Client

� SIP/IMS based architecture (details)

11


� A1p/A2p/MSCe based architecture

12


� A1p/A2p/MSCe based architecture (details)

Inter-MSC handoff

� MSCe – Legacy MSC

Femto-Macro Handoff

� Security gateway to macro network

• IPsec tunnel end-point for femto cell

Femto Security Gateway

Functions

MSCeWhere Call is Anchored

Provided by MSCe1x Supplementary Services

A1p, A2p per 3GPP2 IOS Standards

� Protocols for transporting A1 / A2 signaling and traffic over IP

Interface to Macro Network



MSCe (MSC emulator) deployed

� IP-based MSC

� Support A1p, A2p and interfaces to PSTN, HLR, legacy MSC

BTS, BSC

13


� Split PDSN based architecture for EV-DO

14

� Split PDSN based architecture for EV-DO (details)

� Security gateway to macro network


Femto Security Gateway Functions

A12, A13, A16, A21Optional Interfaces to Macro Network

�Partial PDSN Functions

• Foreign Agent (FA)

•Accounting --UDR Generation

•Authentication (RADIUS)

•QoS policy enforcement

PDSN Core

PDSN in Femto CellPPP Termination Point

� No external A10/A11 establishment, internal to femto cell

� New PPP establishment

� PPP CHAP authentication via Femto Gateway and AAA

� Binding update of new care of address w/ HA for mobile IP

Handoff Impact

RADIUS, MIP via Femto GatewayMandatory Interfaces to Macro Network



No femto-specific

RN, RNC, PCF, some PDSN Functions


15


� PDSN in Macro Network based architecture for EV-DO

AT

1x BSC

IWF

A21

Macro 1x Domain

EV-DO

Femtocell

(RN-RNC-

PCF)

Femto

Security

Gateway

AAA

Untrusted

InternetCable

/ DSL

IPsec

Tunnel(s)

Macro EV-DO Network

PDSNInternet /

Intranet

A12

IP

Macro Network Domain

A13, A16

IP

Femtocell Domain

RNC

IP

NetworkA11

A10

* Mandatory: A10/A11

* Enhanced: A12, A13,

A16, A21

* IPsec tunnel support

* Security gateway –

IPsec tunnel support

PPP

termination

point

16

� PDSN in Macro Network based architecture for EV-DO (details)


A12, A13, A16, A21Optional Interfaces to Macro

Network for Enhanced Capabilities

� Security gateway (firewall) to macro network



Macro PDSNPPP Termination Point

� New A10/A11 establishment

� No PPP re-establishment

•If target RNC re-selects same PDSN upon handoff

Handoff Impact

A10 / A11Mandatory Interfaces to Macro

Network



Macro PDSN used for femto cells

RN, RNC, PCF

17

� PDSN in Femto Cell based architecture for EV DO


18

� PDSN in Femto Cell based architecture for EV DO (details)


A12, A13, A16, A21Optional Interfaces to Macro

Network

� Security gateway (firewall) to macro network



PDSN in Femto CellPPP Termination Point

� No external A10/A11 establishment, internal to femto cell

� New PPP establishment

� PPP CHAP authentication between femto PDSN and AAA

� Binding update of new care of address w/ HA for mobile IP

Handoff Impact

RADIUS, MIPMandatory Interfaces to Macro

Network



No femto-specific

RN, RNC, PCF, PDSN, FA

19

� Airvana proposed two architectures

• Legacy Technology-based Architecture

• SIP/IMS-based Architecture

� Airvana’s preference is the SIP/IMS based architecture

� However, they seemed also ready for the legacy technology base one

Proposed Architectures (Airvana)

20

� Legacy Technology-based Architecture

Proposed Architectures (Airvana 1)

21

� SIP/IMS based architecture

Proposed Architectures (Airvana 2)

22

� CSRV Functions


23

� IMS and legacy network interworking


24

� ALU proposed two architecture

• HRPD Femto Architecture

• 1x Femto Architecture

� ALU did not show any preference to any one of the two architectures

Proposed Architectures (ALU)

25

� HRPD Femto Architecture

� A typical legacy protocol tunneling based architecture

Proposed Architectures (ALU 1)

26

Proposed Architectures (ALU 2)

� 1x Femto Architecture

� This is an IMS-like Architecture

• MFIF: MAP-Femto Interworking Function

• TAS: Telephony Application Server

27

� Starent proposed only one architecture

• Basically a legacy protocol tunneling solution

• Starent’s IMS application still need a SIP AS

Proposed Architectures (Starent)

28

� This is a typical legacy protocol tunneling architecture


Femto

Access

Point

Home

GW

Femto Management System

FAP-MS FGW-MS

Fa

Fixed

Broadband

Internconnect

Fd

Fm Fg

CS core

PS core

Subscriber Databases

Fb-cs-1,2

Fb-ps

Fr

HPLMN Core Network

Common IMSFb-ims

Femto

Access

Point

Mobile

Station

Fd

Ff

Fw

PCRF

Home

GW

FL

FL

Fa

Fe

RAN

Mobile

Station

Fp

SeGW

Femto GW

SeGW

CS��SIP IWF

Media Gateway

CS/PS Proxy

PDSN/FA

29


FGW �� Management System

FAP �� Management System

FAP �� Home Gateway

FGW �� Subscriber Database

FGW �� IMS Core

FGW �� PS Core

FGW �� eCS Core

FGW �� CS Core

FAP �� FGW

Description

� HTTP (not specified in 3GPP2)

� TR-069 (not specified in 3GPP2)

� UPnP (not in 3GPP2 scope)

� A12 for HRPD (AN-AAA)

� RADIUS (AAA)

� Gm/Mw

� MIP, PMIP, Simple IP

� A1p, A2p (IOS 5.0)

� A1, A2 over SS7 (TDM)

� IOS (Ax) over IP

3GPP2 Interface

Ut

Fm

Fl

Fr

Fb-ims

Fb-ps

Fb-cs-2

Fb-cs-1

Fa

Femto Forum Reference

Point

traffic that operator allows to be directed into the

broadband network for routing

FGW �� Fixed Broadband NetworkFe

FAP �� FAP

FGW �� RAN

FGW �� PCRF

Mobile Station �� FAP

Description

� A3/A7 Inter-FAP SHO (e.g., multiple FAPs in home)

� IOS (Ax)

� Ty

� CDMA2000 1x CDMA2000 HRPD

3GPP2 Interface Alignment

Ff

For Further Study

Fw

Fp

Fd

Starent Proposed Reference

30

� Starent Architecture in pre-IMS network


A1

A2

A1p/A2p

1x

A1/2 MSC/VLR

Home NetworkHome Network

BTSBTS

BSCBSC

PCFPCF

FemtoFemto

Security GWSecurity GW

PDSN FAPDSN FA

AxpAxp/Ax Conversion/Ax Conversion

IOS ProxyIOS Proxy

IOS/SIP GatewayIOS/SIP Gateway

RTP RelayRTP Relay

Femto GatewayFemto Gateway

A1p/A2p

A10/A11

BSC

1x

HRPD

AN A10/11

A12/A13/A16/A21

IPSec SA

PDSN

FAMIP

MIP

HLR/

AuC/

HSS

IS-41

IS-41

InternetHome

Agent

AAA

HRPD

MSCe

Data

Services

Core IP

Network

AN-

AAA

A12

A12A13/A16

A21

Simple IP

1x IOS

MSC

IS-41

31

� Starent Architecture in IMS network


1x

A1/2 MSC/VLR

Home NetworkHome Network

BTSBTS

BSCBSC

PCFPCF

FemtoFemto

Security GWSecurity GW

PDSN FAPDSN FA

IOS ProxyIOS Proxy

IOS/SIPIOS/SIP GatewayGateway

RTP RelayRTP Relay

Femto GatewayFemto Gateway

A1p/A2p

A10/A11

BSC

1x

HRPD

AN A10/11

A12/A13/A16/A21

IPSec SA

PDSN

FAMIP

MIP

HLR/

AuC/

HSS

IS-41

Cx

InternetHome

Agent

AAA

HRPD

A1p/SIP

Data

Services

Core IP

Network

AN-

AAA

A12

A12A13/A16

A21

A2p/RTP

1x IOS

CSCF

Convergence

Server

CSRV

VLR

ISC

IS-41

VCCF

WIN

Call

Continuity

Server

ISC

MgMGC

MGW

Gm/SIP

MbVoIP/RevA

VoIP

Rev-A

Simple IP/Gm/SIP

32

� Huawei proposed 3 architectures

• 1x IOS based FemtoCell Architecture

• IMS based FemtoCell Architecture

• EVDO FemtoCell Architecture

� Huawei did not show any preference

Proposed Architectures (Huawei)

33

� 1x IOS based FemtoCell Architecture

� A typical legacy protocol tunneling architecture

Proposed Architectures (Huawei 1)

MS FAP FGW

MSC/ MSCe

MGW

HLR

PDSN

CS

PSHAAA

CS

PS

A1/ A1p

A 2 p

A10/ A11

FAP

� Contains BTS/BSC/PCF function

� Provides A1p/A2p/A10/A11 interface to the FGW

� Support IPSec

FGW

� Proxy of A1p/A2p/A10/A11

� Provide standard A1/A1p/A2/A2p Interface to the MSC

� Provide standard A10/A11 interface to the PDSN

� Support IPSec

34

� IMS based FemtoCell Architecture


MS FAP

FGW

( SI PCl i ent )

MSC/ MSCe

HLR

PDSN

HAAA

CS

PS

A10/ A11

I MS AS

P/ S- CSCF MGCF

MGW MS

HSS

FAP


� Provides A1p/A2p/A10/A11 interface to the FGW

� Support IPSec

FGW

� Proxy of A1p/A2p/A10/A11

� Support SIP client function in order to convert A1p

signaling to SIP signaling

� RTP transport of user traffic


� Support IPSec

35

� EVDO FemtoCell Architecture


MS/ AT FAP FGW

MSC/ MSCe HL R

PDSN HAAAI P S e c

A1 / A1p

A10/ A11

AN- AAA

HRPD AN

1x BSS

A 1 2

A13 / A16

A1/ A2

A 2 1

FAP


� Provides A10/A11/A13/A16/A1p/A21 interface to the

FGW

� Support IPSec

FGW

� Proxy of A10/A11/A13/A16/A1p/A21


� Provide standard A13/A16 interface to the HRPD AN

� Provide standard A1p/A21 interface to 1x system

� Support IPSec

36

� ZTE proposed 4 architectures

• Legacy Based Tunneled A1/A2 Architecture

• Legacy Based Tunneled Abits Architecture

• Legacy Based Tunneled SIP Server Architecture

• SIP/IMS based architecture

� ZTE did not show any preference

Proposed Architectures (ZTE)

37

� Legacy Based Tunneled A1/A2 Architecture

Proposed Architectures (ZTE 1)

38

� Legacy Based Tunneled Abis Architecture


1x AiF

HRPD AiF

39

� Legacy-Based SIP Server Architecture


Mobile IP

Home

Agent

cdma 1x

Mobile

Station

Legacy MS Domain

Support

Other Access Networks

Access Gateway

FA / Attendant

eBS

SRNC

HRPD-AN PDSN

Non-3GPP2

Trusted AN

Non-3GPP2

Un-Trusted AN

HRPD

Access

Terminal

ePDIF

PSTN

IPNetwork

MAPTIA/EIA-41

IPServices

UMB-AN

Femto CellFemto Network

GatewayF1

Aquater

1x AiF

HRPD AiF

PDIF

Call Manager

Legacy Core Network

HLR MSC SCP

F2 F3

A

F4

Media

Gateway

Media

Gateway

Control

Function

IMS Core Network

Call Session

Control

Function

SIP Gateway

40

� SIP/IMS Based Architecture


1x AiF

HRPD AiF

41

� Nortel proposed one architecture

• An IMS based architecture

Proposed Architectures (NT)

42

� Nortel proposed IMS based architecture

• TAS: Telephony application server

Proposed Architectures (NT)

43

Pro IMS v.s. Pro Legacy Protocol Tunneling

Pro IMS CampPro Legacy Protocol

Tunneling Camp

44

May 08 Osaka meeting summary

45


� Consolidation started

� Nortel, Arivana and ALU proposed 1xRTT voice femto network architecture

46


� Qualcomm presented two 1xRTT voice femto network architectures (1)

• 1x voice femto architecture using A1/A1p and A2/A2p

47


� Qualcomm presented two 1xRTT voice femto network architecture (2)

• 1x voice femto architecture using IMS

• This one conforms with the one proposed by Nortel, Airvana and ALU

48


� Qualcomm also presented a HRPD/1x packet femto network architecture

• On top of this architecture, a MIP interface between FAN to HA is proposed

Femto

Gateway MS/

AT

Femto

Cell

PDSN PCRF

Macro RNC/

PCF

A10

A11

A13/A16 (HRPD Only)

HRPD or

1x Packet

Macro

Cell

A10

A11HA

AAA

A12

A12

AN-AAA

MIP

Femto Access Network (FAN)

49

June 08 Cancun meeting summary

50


� Qualcomm, Huawei, Nortel and ALU re-confirmed the HRPD/1x Packet femto

architecture

• MIP interface between FAN to HA was not adopted

51


� Qualcomm initiated discussion on Femto Authentication Options

• different types of credentials for femto systems

– Femto (Device) Credentials

– User (or) AT credentials

• two femto authentication options/approaches

– Shared key Authentication

– Certificate-based Authentication

� Qualcomm also initiated discussion on Femto Provisioning and Registration

• IPComm, LGE, VIA Telecom contribution: Provisioning parameters

• ALU contribution: Femto Management system

• Femto management framework was proposed

52

July 08 Orlando meeting summary

53


� Started drafting the following femto specifications

• X.P0059-000 Femto Overview and Architecture

• X.P0059-100 femto Network Specification

� Approved femto 1xRTT Architecture

Femto

GatewayMS

HLR/

AuC

1x

MSC

MFIF TAS

MGCF/

MGW

SMSC

SIP

(SIP)

Femto Access

Point

SIP

UA

Legend:

TAS – Telephony Application Server

SMSC – Short Message Service Center

MFIF – MAP-Femto Interworking Function

MAP

SIP

Fx3

(RTP)

Fx2

Fx1

AAA

AAA

IMS

SIP

MAP

1x Macro

BSCA2

A11x

Macro

Cell

54


� Approved HRPD/ 1x Packet Data Femto Architecture

Ty

Ty

IP

FGW

AAA

(Axx)

Femto-AAA

MS/AT1xRTT/

HRPD

A11

Internet

MIP

(P)MIP

AAA

(A12)

AN-AAA

AAA

HA/LMA

PDSN

For A12 Device

Authentication

For Femto

Device

Authentication

AAA

For PDS

Authentication

HRPD

AN

FAP

FA/

MAG

A13

A16

-19

SeGW

IP

A10

BS/AN

PCRF

PDST

55


� Qualcomm added PDE, MPC and PSAP elements into the 1x voice femto

architecture reference model

PDE – Position Determining Entity

MPC – Mobile Positioning Center

PSAP – Public Safety Answering Point

56


� Qualcomm added IMS core into the HRPD/1x Packet femto architecture

reference model

57

Femto

GatewayMS

HLR/

AuC

1x

MSC\

MSCe

MFIF TAS

MGCF/

MGW

SMSC

SIP

(SIP)

Femto Access

Point

SIP

UA

Legend:

TAS – Telephony Application Server

SMSC – Short Message Service Center

MFIF – MAP-Femto Interworking Function

MAP

SIP

Fx3

(RTP)

Fx2

Fx1

AAA

AAA

IMS

SIP

MAP

1x Macro

BSCA2

A11x

Macro

Cell A1/A1p

A2/A2p


� Sumsung suggested to add A1/A1p and A2/A2p interfaces between FGW and

MSC/MSCe in 1x voice femto architecture reference model

58


� Sumsung suggested to add MSC/MSCe and PCF elements and

corresponding interface in HRPD/1x packet femto architecture reference

model

Ty

Ty

IP

FGW

AAA

(Axx)

Femto-AAA

MS/AT1xRTT/

HRPD

A11

Internet

MIP

(P)MIP

AAA

(A12)

AN-AAA

AAA

HA/LMA

PDSN

For A12 Device

Authentication

For Femto

Device

Authentication

AAA

For PDS

Authentication

HRPD

AN

FAP

FA/

MAG

A13

A16

-19

SeGW

IP

A10

BS/AN

PCRF

PDST

MSC/

MSCe

A1/A1p

PCFA9A8

A11

A10

59

July 08 orlando meeting summary

� Airvana started proposing the second phase of recommendations based on

the approved femto architecture reference models on the following aspects:

• Femto Gateway Functions (Security, Authentication)

• Proposed PDSN based Femto-FNG tunneling model

• Proposed high level call flow for tunnel establishment and MS/AT registration,

1x voice service access, HRPD service access, on going FAP management

etc.

• Other misc. recommendations

3GPP2 Femto Architecture Summary (January â€“July 2008)

Documents

Transcript of 3GPP2 Femto Architecture Summary (January â€“July 2008)