SOURCE: Dennis Ong, Alcatel-Lucent Donna Sand Alcatel-Lucent

CONTACT: hdong@alcatel-lucent.comdsand@alcatel-lucent.com

ABSTRACT: This contribution defines the services that interface between the femtocell and the IMS core network with the goal of having open services interfaces to support multi-vendor femtocell

TITLE: IMS Services for Femtocell

3GPP2 Femto Cell Workshop

RECOMMENDATION: <Discuss and Adopt / FYI >

Alcatel-Lucent grants 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. Alcatel-Lucent is 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 Alcatel-Lucent 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 Alcatel-Lucent. Alcatel-Lucent specifically reserves the right to amend or modify the material contained herein and to any intellectual property of Alcatel-Lucent other than provided in the copyright statement above.

S00-FEMTO-20070915-006 <IMS Services for Femtocell>

2 | October 15-16, 2007

Objectives

To define the services architecture between the femtocell and the IMS Core Network (IMS CN) that will enable a multi-vendor femto environment.

The services are: Phase 1

1x voice Handoffs – Two options– SIP/MAP (ANSI-41): Support Macro <-> Femto, Femto <-> Femto

– A21/Voice Call Continuity(VCC): Only support Femto -> Macro

Services Interworking – Femto emulates SIP simple endpoint to IMS CN

– Proposed Interworking Call Flow example shown in following slides (call hold without announcement)

Short Message Service Interworking– Support using both TSG-X X.P0048 SIP MESSAGE and MAP SMDPP

– Proposed Interworking Call Flow described in following slides

Phase 2 -- VCC for support of domain transfer (handoff) between HRPD in the Femto to 1X in the macro network environment Support using TSG-X X.P0042 standard

3 | October 15-16, 2007

Femtocell Architecture

BSR Femto

DSL orCable

Network

FemtoOA&M

Router/Modem

AAA

PrivateIP Network

PSTNHLR

3G-1XMSC

HA

FemtoNetworkGateway

IMS Core

Femto Network Macro Network

HRPDRNC

SMS- GW

4 | October 15-16, 2007 Alcatel – Lucent ProprietaryAlcatel – Lucent Proprietary

Short Message Service (SMS) InterworkingMobile Originated SMS

UE1 Femto IMS CN HSS SMS-GW

Mobile Originated Short Message Service (MO SMS) from UE1

(M1) Data Burst Message (DBM)

(M2) SIP MESSAGE

(M3) SIP MESSAGE

(M4) SIP 202 ACCEPTED

(M5) SIP 202 ACCEPTED

(M6) SIP MESSAGE (Delivery Ack)

(M7) SIP MESSAGE (Delivery Ack)

(M8) Data Burst Message (DBM) (Delivery Ack)

(M9) SIP 200 OK

(M10) SIP 200 OK

5 | October 15-16, 2007 Alcatel – Lucent ProprietaryAlcatel – Lucent Proprietary

Short Message Service (SMS) InterworkingMobile Terminated SMS

UE1 Femto IMS CN HSS SMS-GW

Mobile Terminated Short Message Service (MT SMS) delivery for UE1

(M1) UDR

(M2) UDA

(M3) SIP MESSAGE

(M4) SIP MESSAGE

(M5) Data Burst Message (DBM)

(M6) SIP 200 OK

(M7) SIP 200 OK

6 | October 15-16, 2007

Call Hold Without Announcement

Alcatel – Lucent ProprietaryAlcatel – Lucent Proprietary

Stable call in talk state between UE1 (3G-1X UE accessing a Femto) and UE2 (IMS compliant UE)

UE1 Femto P-CSCF S-CSCF AS UE2

(M1) Flash message

(M2) ReINVITE (sendonly)

(M3) ReINVITE (sendonly)

(M4) ReINVITE (sendonly)

AS determines no announcement will be played

(M5) ReINVITE (sendonly)

(M6) ReINVITE (sendonly)

(M7) ReINVITE (sendonly)

(M8) 200 OK (recvonly)

(M9) 200 OK (recvonly)

(M10) 200 OK (recvonly)

(M11) 200 OK (recvonly)

(M12) 200 OK (recvonly)

(M13) 200 OK (recvonly)

(M14) ACK

(M15) ACK

(M16) ACK

(M17) ACK(M18) ACK

(M19) ACK