Copyright Alcatel-Lucent 2008 - All Rights Reserved 1 X50-20080331-xxx Common Femto Architecture Alcatel-Lucent Discuss and Adopt. 3GPP2 Super Meeting

Copyright © Alcatel-Lucent 2008 - All Rights Reserved

1

X50-20080331-xxx

Common Femto ArchitectureAlcatel-Lucent

Discuss and Adopt.

3GPP2 Super MeetingMontreal, Quebec, Canada

March 31 – April 4, 2008


2

COPYRIGHT STATEMENT:

The contributors grant a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. The contributors are also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution.

This document has been prepared by the contributors to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on the contributors. The contributors specifically reserves the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the contributors other than provided in the copyright statement above.


3

HRPD Femto Architecture– Highlights and Benefits

1x Femto Architecture– Highlights and Benefits

HRPD Femto Architecture Flows Flows Using The 1x Femto Architecture

– Constraints and Assumptions– Registration– Authentication– Call Setup– Hand-in (Macro to Femto)– Hand-out (Femto to Macro)– Supplementary Services– SMS

Conclusion and Recommendation

OUTLINE


4

HRPD Femto Architecture

Femto Gateway

MS/AT

FemtoCell

PDSN

AAA

Macro AN/PCF

A10

A11

A12

A13 A16

HRPD

MacroCell

A10

A11


5

HRPD Femto Arch. Highlights and Benefits

The HRPD Femto Architecture takes advantage of standard interfaces:

– The HRPD radio interface– A10 and A11 to the PDSN– A12 to the AAA for RAN level authentication– A13 and A16 for dormant and active session transfer

Benefits:– Reuse of existing core network entities, AAA and PDSN– Standard HRPD Hard Handoff for Femto to/from Macro


6




– Constraints and Assumptions – Registration– Authentication– Call Setup– Hand-in (Macro to Femto)– Hand-out (Femto to Macro)– Supplementary Services– SMS


OUTLINE


7

1x Femto Architecture

Femto GatewayMS Femto

Cell

HLR/AuC

Macro 1x BSC

1x

MacroCell A2

A1

MSC

P-CSCF S-CSCF

MFIF TAS

MGW

HSS/AAA

SMSC

SS7

SS7

SIPA21

IWFA2

A1


8

1x Femto Arch. Highlights and Benefits Uses standard IMS features

– P/S-CSCF, HSS/AAA– Telephony Application Server (TAS)

MFIF (MAP-Femto Interworking Function)– Resides as an Application Server within IMS– Can access the HLR/AuC and HSS/AAA– Can access the Short Message Service Center (SMSC)

Benefits:– Supports 1x Handoff from Femto to Macro (VCC)– Provides a migration to full IMS and all its features– Using existing CDMA infrastructure to support regulatory

services (E911).


9






OUTLINE


10

HRPD Femto Architecture FlowsGiven that the HRPD Femto System will appear to the

core network as a set of HRPD AN/PCFs, andGiven that the HRPD Femto System will support the

standard A10/A11/A12/A13/A16 interfaces, thenThe flows already defined in A.S0008/A.S0009 for

registration, authentication, call setup, hard handoff, and supplementary services fully apply.


11






OUTLINE


12

Constraints and AssumptionsNo changes to CDMA handsets.

Avoid modifying IMS Core Network and HSS.

MFIF (MAP-Femto Interworking Function) acts as VLR MSC from ANSI41 macro cellular network point of view. TAS (Telephony Application Server) provides services.

Femto provides CDMA to IMS SIP conversion, thus the IMS UA (one or more) is in the Femto.

Each CDMA user is dynamically assigned an IMS UA when it registers on the Femto.

The MFIF registers each CDMA user with the HLR and stores associated data for that user including VLR profile, current Femto ID, etc. in MFIF local data referred to as “VLR”.

The MFIF provides the conversion between Femto-cell ID and CDMA mobile ID.

The 1x global RAND challenges sent over the air in the registration, call origination and call termination system accesses should directly or indirectly be generated by the core network and not the femto for security reasons. A proposal to generate these global RANDs securely is described in the contribution to TSG-S WG4. (See S40-20080218-003.)


13

Femto Authentication/Registration in IMS

S-CSCFP-CSCF

MFIF

FNG

HLR/AuC

SIP UAFemto-1234

Femto Cell

IPsec

[email protected]

HSS

DN 630-555-1111MIN 312-606-1111

2) SIP Register (Femto-1234, IMS Authentication, ….)

1) Femto boot up or re-register due to timer.

TAS

3) 3rd Party Register (Femto-1234)

MFIF = MAP-Femto Interworking Function

TAS = Telephony Application Server


14

User Authentication/Registration in IMS

ToddDN 630-555-1111MIN 312-606-1111

S-CSCFP-CSCFMFIF

FNG

HLR/AuC

SIP UAFemto 1234

Femto Cell

IPsec

1) register

2) SIP MESSAGE (Femto-1234, MS ID, parameters, …)

3) MAP AUTHREQ & REGNOT

VLR: DN 630-555-1111MIN 312-606-1111Femto-1234

DN 630-555-1111MIN 312-606-1111LSP: IMS MFIF

MIN 312-606-1111

[email protected]

4) SIP MESSAGE (Femto-1234, MS ID, Success, …)


15

Femto Notified When User Registers Elsewhere

Todd

S-CSCFP-CSCFFNG

Femto Cell

IPsec

1) Mobile Registers at new location – either Femto or other MSC

2) SIP MESSAGE (old FEMTO ID, MIN or MDN, New Reg.Indication)

HLR/AuC

MFIF or 1b) Mobile Registers on a different Femto ID1c) VLR is removed

1a) REGCAN from HLR

3) The Femto will initiate an IMS deregistration for that IMS UA if appropriate.

DN 630-555-1111MIN 312-606-1111


SIP UAFemto 1234

MIN 312-606-1111


16

CDMA2000 1x Origination

ToddDN 630-555-1111MIN 312-606-1111

S-CSCFP-CSCFFNG

Femto Cell

IPsec

1) origination

2) SIP INVITE (Femto-1234, MS ID, Parameters)

4) SIP INVITE (Femto-1234, CPN, MS ID, …)

HLR/AuC


3) MFIF Authenticates CDMA user with HLR/AuC Allow or Cancel call depending on result

MFIF TAS

SIP UAFemto 1234

MIN 312-606-1111


17

CDMA2000 1x Termination

Todd

S-CSCFP-CSCF MFIFFNG

DN 630-555-1111MIN 312-606-1111

LSP: IMS MFIF

HLR/AuC

Femto BSR

IPsec

1) INVITE (TLDN)

4) Page & Auth

0) ROUTEREQ (MIN)

MFIF TAS3b) SIP INVITE (Femto-1234, MS ID, …)

5) SIP 18x (Parameters)

3a) MFIF Authenticates CDMA user with HLR/AuC

DN 630-555-1111MIN 312-606-1111

SIP UAFemto 1234

MIN 312-606-1111

2) SIP INVITE (Femto-1234, MS ID…. )

VLR: DN 630-555-1111MIN 312-606-1111Femto-1234


18

1x Femto Arch. Flows: Hand-out (Femto to Macro)

AM

1) BSR-Femto advertises neighbor list 3) makes HO decision based on mobile pilot measurements.

IP Network

MFIF

5) Reconfiguration of call during HHO

MGCF/MGW

ANSI41

3G-1XMSC

IVT

PSTN

4) ANSI41 Intersystem Hard Handoff Procedures

MGCF IVTMGW

Original Call Path

After HO Call Path

• MFIF: MAP Femto Interworking Function• AM: Application Manager & Registrar• IVT: Inter-Vendor Trunk• MGCF IVT: MGCF for IVT

2) Mobile monitors pilot strength of neighbor cells and reports to BSR-Femto

A-IMS

Femto


19

1x Femto Arch. Flows: Hand-out (Femto to Macro)

S-CSCFP-CSCF

MFIF

FNG

HLR/AuC

SIP UAFemto-1234

Femto Cell

IPsec

DN 630-555-1111MIN 312-606-1111

2) SIP MESSAGE (HO Required information)6) SIP MESSAGE (HO Command information)10) BYE

1) Femto determines handoff is needed based upon received pilot strength measurements.

7) HO Direction

TAS

3) INVITE (IVT)

3G-1X Cell 3G-1X MSC

MGCF

4) ANSI-41 FACDIR29) ANSI-41 MSONCH

5) HO Request8) HO

Complete


20

1x Femto Arch. Flows: Hand-in (Macro to Femto)

Femto

AM

1) Macro cell advertises neighbor list 3) makes HO decision based on mobile pilot measurements.

IP Network

MFIF

MGCF/MGW

ANSI41

3G-1XMSC

IVT

PSTN

4) ANSI41 Intersystem Hard Handoff Procedures

MGCF IVTMGW

Original Call Path

After HO Call Path

• MFIF: MAP Femto Interworking Function• AM: Application Manager & Registrar• IVT: Inter-Vendor Trunk• MGCF IVT: MGCF for IVT

2) Mobile monitors pilot strength of neighbor cells and reports to Macro cell

A-IMS


21

1x Femto Arch. Flows: Hand-in (Macro to Femto)

S-CSCFP-CSCF

MFIF

FNG

HLR/AuC

SIP UAFemto-1234

Femto Cell

IPsec

DN 630-555-1111MIN 312-606-1111

4) SIP INVITE to setup call path5) SIP MESSAGE (HO Request information)6) SIP MESSAGE (HO Complete information)

1) 3G-1X determines handoff is needed

8) HO Direction

TAS

3G-1X Cell 3G-1X MSC

MGCF

3) ANSI-41 FACDIR29) ANSI-41 MSONCH

2) HO Required

7) HO Comman

d


22

CDMA2000 1x SMS Origination

Todd

S-CSCFP-CSCFFNG

Femto Cell

IPsec

1) SMS origination

2) SIP MESSAGE (CdPN, MS ID SMS Body, …)

4) SMDPP (SMS) HLR/AuC


3) MFIF Authenticates CDMA user with HLR/AuC

MFIF

SMS-C

5) SIP MESSAGE (Femto-1234, MS ID, SMS ACK)

DN 630-555-1111MIN 312-606-1111

SIP UAFemto 1234

MIN 312-606-1111

6) SMS Ack


23

CDMA2000 1x SMS Termination

Todd

S-CSCFP-CSCFFNG

HLR/AuC

IPsec

4) Unique Challenge

1) SMDPP (MIN)

MFIF 5) SIP MESSAGE (AUTHU)

2) AUTHREQ (unique challenge)

SMS-C

3) SIP MESSAGE (Unique Challenge)

6) SIP MESSAGE (SMS) 8) SIP MESSAGE (SMS ACK)

7) SMS & ACK

9) SMDPP (ACK)

Femto Cell

SIP UAFemto 1234

MIN 312-606-1111

VLR: DN 630-555-1111MIN 312-606-1111Femto-1234


DN 630-555-1111MIN 312-606-1111


24

1x Femto Arch. Flows: Supplementary Services -- Flash to Initiate 3 Way Call

Todd

S-CSCFP-CSCF MGCFFNG

DN 630-555-1111MIN 312-606-1111

LSP: IMS MFIF

HLR/AuC

Femto BSR

IPsec

2) re-INVITE (put far party

on hold)

MFIF TAS

DN 630-555-1111MIN 312-606-1111

SIP UAFemto 1234

MIN 312-606-1111

1) SIP INFO (Flash Information )


25






OUTLINE


26

Conclusion The HRPD Femto Architecture can take advantage of existing

interfaces, and reduces the introduction of new network elements (PDSNs) into the operator’s network.

The 1x Femto Architecture proposed here provides a clean path to use of full IMS capabilities.

Recommendation:Review and Adopt these as 1x and HRPD Femto Architectures.

Documents

Copyright Alcatel-Lucent 2008 - All Rights Reserved 1 X50-20080331-xxx Common Femto Architecture Alcatel-Lucent Discuss and Adopt. 3GPP2 Super Meeting