ABSTRACT: This contribution offers some suggestions for the support of Femto Devices in 3GPP2 standards.

TITLE: Femto Device Support

TSG-A WG4

RECOMMENDATION: Note.

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

DATE: July 23, 2007

Notice

SOURCE: Samsung : Bill Semper, b.semper@samsung.com, 972-761-7996

X50-20070723-xxx SS_Femto_Device_Support.ppt

2

Summary

Suggestions for Architecture Assumptions Rationale for Allowing Options Mobility Architecture Possible Evolution Paths Possible Standards Impacts

3

Suggestions for Architecture Assumptions

In X10-20070618-012, Airvana proposed a SIP-based Femto device solution that utilizes IMS

All IP/SIP/MMD based beyond the Femto device

We agree that this is worthwhile, but we would also like to see the standard support Femto devices that utilize an IOS V5.x connection to the network

Proposal for architecture option: IOS V5.x IP-based interface from the Femto device to an MSCe in the operator’s network.

4

Architecture Assumptions (SIP-Based) - 1

Femto Device (UE)

Home/Residential Network

Internet

Edge/AccessNetwork

MMD CoreNetwork

P-CSCF

S-CSCF I-CSCF

VCC AS MGCF

MGW

HSS

Security Gateway

(PDIF)

HA

SIP signaling/RTP bearer

3G1x circuit voice call

5

Architecture Assumptions (SIP-Based) - 2

Femto Device (P-CSCF)

Home/Residential Network

Internet

MMD CoreNetwork

I-CSCF

S-CSCF

VCC AS MGCF

MGW

HSSHA

SIP signaling/RTP bearer

3G1x circuit voice call

6

Architecture Assumptions (IOS-Based) - 1

Femto Device

Home/Residential Network

Internet

Edge/AccessNetwork

CoreNetwork

MSCe

Security Gateway

(PDIF)

MGW

IOS V5.x signaling/RTP bearer

3G1x circuit voice call

7

Architecture Assumptions (IOS-Based) - 2

Femto Device

Home/Residential Network

Internet

Edge/AccessNetwork

MMD CoreNetwork

AGCF like border

function (IOS-SIP)

IOS V5.x signaling/RTP bearer

3G1x circuit voice call

8

Architecture Assumptions (Rationale) Operators who have not yet invested in MMD or have not yet achieved

feature parity on MMD with MSC/WIN-based solutions will benefit.

Leverages legacy service investment

Decouples completely (allows for freedom from legacy services) the services and environments provided over pure IP handsets and legacy circuit based systems.

Very little delta standards development is necessary other than specifying the specifics of the IP transport options of each interface (may already be in place).

Allows for core network evolution to MMD with little to no impact to IOS or deployed Femtos

Can be standardized relatively quickly

Allows Femto Devices to provide full complement of circuit switched services immediately

9

Mobility Architecture We support the VCC/A21 solution proposed by Airvana as one option in

the Femto device standard

We would also like to see an option that allows for IOS V5.x signaling through MSCe

This would probably require almost no changes to the IOS

Would leverage existing infrastructure investments

By allowing the option for both architectures, standard could support migration paths and so be more useful

10

Standards Impacts We support Airvana’s proposal for standards text modification

IOS impacts will be negligible for our option, if needed at all