Upload
deirdre-morrison
View
217
Download
0
Embed Size (px)
Citation preview
cdma2000 FemtoStandardization Activities
in 3GPP2
…
Femtocell World Summit
June 21st-23rd, 2011
London, UK
2
Background
• 3GPP2 began work on femtocell-related standardization in early 2007– Kicked off through a femtocell workshop in October 2007 in
Boston
• Technical activities were initiated in all 3GPP2 TSGs in late 2007– System requirements– Security aspects– Air-interface (radio) enhancements– Support for legacy 1x circuit services– Packet data services for 1x and HRPD (EV-DO)
• Phase I femtocell specifications completed by Q1 2010• Phase II specs support femtocells connecting to
MSC/MSCe, to be completed Q2 2011
3
3GPP2 Standards : Architecture
• Two possible architectures for voice– Legacy IOS interface connecting to existing MSC/MSCe– SIP/IMS approach for connecting femtocells to IMS
convergence server
• Packet data service model– Reuse existing interfaces (A10/A11) to PDSN from Femto
Access Points (FAPs)
• Security architecture using IPsec/IKEv2– Certificates with simple authentication model– Basic IPsec/IKEv2 profiles
• TR-069-based management architecture– Specification of Management Object contents and procedures
4
3GPP2 Femtocell System Architecture (IMS)
FemtocellAccessPoint(FAP)
SecurityGatewayMS/
AT
1x or HRPD Air Interface
IPsecTunnel
PDSN A10/A11
AAA
HA
IP Network
SIP/IMS/RTP
IMS
FemtocellConvergence Server
(FCS)
ANSI-41/MAP
MSC HLR/VLR
A13,A16-19
FemtoGateway(FGW)
A13,A16-19
HRPDRNC
Femto-AAA
AN-AAA
A12
FemtocellConvergence
Server(FCS)
FemtoGateway(FGW)
Femto-AAA
RIPA
Home IP Network
LIPA
FemtoManagement
System(FMS)
TR
-069/TR
-196A26
5
3GPP2 Femtocell System Architecture (Legacy IOS-based)
FemtocellAccessPoint(FAP)
SecurityGatewayMS/
AT
1x or HRPD Air Interface
IPsecTunnel
PDSN A10/A11
AAA
HA
IP Network
ANSI-41/MAP
MSCe HLR/VLR
A13,A16-19
FemtoGateway(FGW)
A13,A16-19
HRPDRNC
Femto-AAA
AN-AAA
A12
FemtoGateway(FGW)
Femto-AAA
RIPA
Home IP Network
LIPA
FemtoManagement
System(FMS)
A1p/A2p
A1p/A2p/A25/A26
6
3GPP2 Standards : Key Features
• Preferred User Zone List (PUZL) as part of Enhanced System Selection (ESS)
– “Fingerprint” of the FAPs location to assist autonomous scanning and selection of FAPs
– Facilitate manual selection, black list and white list management in terminals
• Active handoff from macro to FAP– Legacy terminals supported through the reverse-link detection of mobile
signal or out-of-band detection– Enhanced terminals supported through the new overhead message that
advertises unique FAP identity
• Air interface enhancements for 1x and EV-DO– Operates with unmodified macro systems (1x and EV-DO)– Allows flexible partitioning of PN code space between macro system
and femto system– Augmented overhead for quick discovery of unique femto identity,
association type, human-friendly ID, location information
7
3GPP2 standards: LIPA and RIPA
Femto /Router
handset in femto coverage
PDSN
MediaServer
Printer
TV
Home IP Domain
Operator’s Backhaul
handset in macro network
Operator’sIP Domain
InternetInternet
Residential Backhaul (Firewall)
WWW
8
Role of The TR-069 Standard in Femtocell Management
• Broadband Forum TR-069 has been selected as the framework for femtocell management– Widely supported by 3GPP2 (and 3GPP) vendors and carriers– Endorsed by Femto Forum
• Functions controlled via provisioning– Discovery/Registration– Redirection to alternate SeGW, ACS, or Femto Gateway– Self-organizing network– Location verification– Provisioning and radio parameter assignments
• 3GPP2 FAP device management model is included as part of TR-196 issue 2 – to be published soon
9
3GPP2 Femtocell-Related Specifications
• System Requirements for Femto Cell Systems – S.R0126-0 v1.0
• Femtocell System Overview – S.R0139-0– Providing guideline to operators on deployment considerations for cdma2000 femtocells
• Interoperability Specification (IOS) – A.S0024– Includes handin/out, IOS interface support for connecting to MSC/MSCe
• Packet Data Service pieces – X.S0059– Packet data service aspects for 1x and EV-DO– Local and Remote IP Access support– SIP/IMS-based 1x legacy voice service
• Femto Management Objects – X.R0063 (subset of TR-196 issue 2)
• Network Reference Model, etc., – S.R0135
• Security Framework – S.S0132
• Air Interface Enhancements for future femto-aware mobile devices– EV-DO – C.S0024-C– 1x enhancement – C.S0005-E– Enhanced System Selection (ESS, a.k.a. PUZL) – C.P0016-D– Signaling conformance tests
• Performance requirements for FAPs
10
BACKUP SLIDES
11
3GPP2 Organization Structure and Roles in Femtocell-Related Work
3GPP2Organizational Partners/
Steering Committee
TSG-AAccess Network
Interfaces
TSG-CRadio Access
TSG-SService and System
Aspects
TSG-XCore Networks
• IOS-based femtocell interface• Device Authentication• RAN Management Objects• Interworking between femto and macro systems
• Enhanced System Selection• 1x and EV-DO Radio Interface Enhancements• Minimum Performance Specifications• Air Interface Management Objects
• System Requirements• Femtocell System Overview• Security Architecture• 3GPP2 Program Management• 3GPP2 Vision• Network Reference Model• System Management Model
• Femto MO Ad Hoc Group • Packet Data Service Aspects• Security Protocols• Reference architecture for femtos• SIP/IMS-based Circuit Service Architecture and Protocols• IP-related Management Objects
Femto Forum
MRPRelationship
12
Femtocell Management Standardization Process
FemtoForum
3GPPRAN3->SA5
3GPP2TSG-X/A/C->
FMOAHG TR-196Femto Mgmnt Objects
Mgmnt ObjectFramework
BroadbandForum3GPP AI MO
Contents(UMTS, LTE)
3GPP2 AI MOContents
(1x, EVDO)
3GPP SpecificProcedures(Disc., etc.)
3GPP2 SpecificProcedures(Disc., etc.)
Mgmnt ObjectFramework
TR-069Framework