Upload
gabriella-dixon
View
232
Download
0
Embed Size (px)
Citation preview
1
3GPP TSG SA Chairman3GPP TSG SA Chairman Stephen HayesStephen Hayes
3GPP System Architecture Evolution
ATIS LTE ConferenceJanuary 26, 2009
2
3GPP Directions
Radio Network Core Network
•Faster Data rates
•Decreased Latency
•High Cell Edge Throughput
•Spectrum Flexibility
•Access independence for services
•Standardized multimedia services
•Mobility and IP interworking for all accesses
FASTER
Wider S
cope
3
Continuous improvement of access technologiesProvision of services over any access network
Common Core network
GSM 900
3G HSPA
WLAN E-UTRANEDGE
GSM 1800
GPRS
GSM 1900
GSM ph.1 R97 R98 R99 Rel-5/6 Rel-6/7 Rel-8 and onwards
WiMAX?
?
Evolved RA N S 1
GERAN
UTRAN
GPRS Core G b
I u
S 3
S 8
S 2
S7 Rx +
Home EPC MME UP E
S 6
Op . IP Serv (IMS, PSS, etc.)
Home Inter AS Anchor
HSS S 6
non 3GPP WLAN
S4
S 2
vPCRF
S 7
hPCR F
Visited Network
Home Network
S 9
Visited EPC
Evolved RA N S 1 SGi
UTRAN I u
S 3
S 8
S 2
Rx +
Home EPC MME UP E
S 6
Op . IP Serv (IMS, PSS, etc.)
Home Inter AS Anchor
HSS S 6
non 3GPP WLAN
S 2
vPCRF
S 7
hPCR F
Visited Network
Home Network
S 9
* Color coding: red indicates new functional element / interface
3GPP Anchor
SGSN
S5a
From GSM to multi-access
Fixed
PacketCable
4
Broadband Accesses They come in many flavors
xDSL
Fiber (PON & P2P) Fiber/VDSL2
Fixed WirelessHSPA/LTE
Satellite/Terrestrial
Unlicensed (WiFi, etc)
Others
Cable (DOCSIS2 3)
Fixedaccess
Fixed/nomadicwireless
Mobileaccess
WCDMA/HSPA
LTE
CDMA2000 EVDO
GSM/EDGE
The borderline between fixed and mobile is getting less clear
Mobile WiMax
Others
5
3GPP Approaches to Multi-Access
Service Convergence using Common IMS
Session ConvergenceUsing Evolved Packet Core (EPC)
EPC
Transport
Mobility
Core Functions:
- IP session ctrl- Mobility support- Deep Packet Inspection- Security- Charging- Policy and Resource control
Accessinter-
workingfunctions
RGW
Wirelineaccess
Wirelessaccess
Standard Services & IMS
Fixed Core Network
Transport
Mobility
Core Functions:
- IP session ctrl- Deep Packet Inspection- Security- Charging- Policy and Resource control
RGW
Wirelineaccess
Wirelessaccess
Mobile Core Network
Core Functions:
- IP session ctrl- Mobility support- Deep Packet Inspection- Security- Charging- Policy and Resource control
Wirelessaccess
Standard Services & IMS
6
Service Convergence using IMS/Common IMS
Fixed Core Network
Transport
Mobility
Core Functions:
- IP session ctrl- Deep Packet Inspection- Security- Charging- Policy and Resource control
RGW
Wirelineaccess
Wirelessaccess
Mobile Core Network
Core Functions:
- IP session ctrl- Mobility support- Deep Packet Inspection- Security- Charging- Policy and Resource control
Wirelessaccess
Standard Services & IMS
Service Convergence
7
IMS/Common IMS
1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009
UMTS (3G) HSPA DL HSPA UL LTE
• IMS developed as part of 3GPP Rel 5 as an application development environment– Encourage new applications to use environment
– Greater operator policing than native SIP/SDP
– Home control allowing customization
• IMS retargeted in Rel 7 for telephony replacement– Standardized multimedia suite developed
– Optimizations to improve performance
– Access independence
• Common IMS specified in Rel 8– Integration of IMS variants and requirements from 3GPP2, TISPAN, and Cablelabs
IMS MMTel Common IMS
8
Internet
IP Multimedia Subsystem (IMS)• PS domain IP Multimedia service platform
• Based on open IETF standards– End to end IP (SIP)– Multi access
• GPRS, I-WLAN, fixed xDSL, Packet Cable defined
• More access technologies to follow...
Circuit-switched network
(2G or 3G)IP
MultimediaCore
PSTN
IP connectivity
(GPRS, 3G,...)
Find & route to destination
User data
Any IP connectivity (3G, WLAN,...)
End-to-End IP services
9
• 3GPP members, 3GPP2, WiMAX forum, ETSI TISPAN and CableLabs contribute to 3GPP common IMS specifications– Different requirements are supported in common implementation
• All IMS specifications are harmonized to 3GPP specifications– Common parts are defined in 3GPP specifications only
• Core IMS entities (CSCFs, AS, UE IMS client,...) + agreed common functions
– Other organisations either reference or re-use 3GPP specification as it stands
– Any changes or additions in the Common IMS area are made in 3GPP• All 3GPP members can contribute on their favourite work items• Ongoing work initiated by 3GPP members, CableLabs, 3GPP2 and ETSI TISPAN
– The scope and coverage of Common IMS have been agreed by the SDOs
• Common version of IMS specifications in Rel-8– Business or architecture specific additions to 3GPP Common IMS are possible
outside the agreed Common IMS area
Common IMS
10
Multimedia Telephony Service• Multiple Simultaneous Media Streams
– Voice– Text– Video– File Transfer– Video/Photo/Audio Sharing
• Multimedia analogs of traditional PSTN supplementary services– Originating Identification Presentation (OIP)– Originating Identification Restriction (OIR)– Terminating Identification Presentation (TIP)– Terminating Identification Restriction (TIR)– Malicious Communication IDentification (MCID) – Anonymous Communication Rejection (ACR) – Communication Diversion (CDIV)– Communication Waiting (CW) – Communication Hold (HOLD)– Communication Barring (CB)– Completion of Communications to Busy Subscriber (CCBS) – Message Waiting Indication (MWI)– Conference (CONF)– Advice Of Charge (AOC) – Explicit Communication Transfer (ECT)– Reverse charging – Closed User Group (CUG) – Three-Party (3PTY)
11
But what if you need?
• Session Continuity• Mobility for non IMS applications• Common IP level services
– Filtering– Deep Packet Inspection– Firewall
• Common Management
12
Session ConvergenceUsing Evolved Packet Core (EPC)
EPC
Transport
Mobility
Core Functions:
- IP session ctrl- Mobility support- Deep Packet Inspection- Security- Charging- Policy and Resource control
Accessinter-
workingfunctions
RGW
Wirelineaccess
Wirelessaccess
Standard Services & IMS
Session Convergence
13
Examples of non-IMS apps
• Multimedia Broadcast Messaging Service (MBMS)
• High Quality Audio• Packet Streaming
14
• LTE = E-UTRAN = evolved radio network– Megabit class data rates– Short delays– Short transition from idle to active
• SAE = System Architecture evolution– SAE is the project name, the evolved network is called EPC– Evolved IP oriented multi access architecture
• E-UTRAN integrates only to SAE, A/Gb or Iu not possible• Strongly IP based PS only network• EPC covers both 3GPP and non-3GPP access technologies• Seamless roaming between E-UTRAN, 2G and 3G (tight interworking)• Loose interworking with non-3GPP accesses• GTP solution for intra-3GPP mobility and IETF based solution for
non-3GPP mobility– The main Architecture specifications 23.401 and 23.402 frozen in June 2008– Protocol work is ongoing and frozen with exceptions in December 2008
System Architecture Evolution (SAE)
15
Convergence Using EPC
Evolved Packet Core
WirelineAccess
WirelessAccess
Partnerservices
Firewall/Security services
Content/Service filtering
QoS and Bandwidth mgmt
IP level service control
Uniform service/QoS treatmentAcross accesses and devices
Friends house
Roaming partner
OperatorServices
(e.g. IPTV,VoIP, ....)
• Mobility and ubiquity adds value to all services• Individualizing all services• Consistent experience across accesses and devices• Bundling different fixed, fixed wireless and mobile
subscriptions• Access and device awareness
default(per bundle)
individualized
Internet
Charging
16
S6a
HSS
S8a
S3 S1-MME
S10
UTRAN
GERAN SGSN
MME
S11 Serving Gatew ay UE
“ LTE - Uu ” E-UTRAN
S12
HPLMN
VPLMN
PCRF S7 Rx
+ SGi •Operator’s IP
Services (e.g. IMS, PSS
etc.)
PDN Gatew ay
S1-U
S4
Mobility anchor
Packet routing
Idle mode packet buffering & DL
initiation
Legal interception
UE IP address allocation
Packet screening & filtering
Policy enforcement
Charging support
Legal interception
NAS signaling+sign. security
Mobility between 3GPP ANs
Idle mode UE reachability
P-GW and S-GW selection
SGSN selection at HO
Authentication
Bearer establishment
SAE architecture (23.401)
User planesecurity(UMTS AKA)
Signalingsecurity(UMTS AKA)
17
Trusrted*
Non-3GPP IP Access
or 3GPP Access
SGi
PCRF
S7
S6a
HSS
ePDG
S2b
Serving Gateway
Wn*
3GPP AAA
Server
Operator’s IP Services
(e.g. IMS, PSS etc.)
Wm*
Wx*
Untrusted
Non-3GPP IP Access
Trusted
Non-3GPP IP Access
Wa*
Ta*
HPLMN
Non-3GPP Networks
S1-U
S1-MME
EUTRAN
2G/3G SGSN
S4
S3
S5S6c
Rx+
Rx+
S2a
PDN Gateway
MMES11
S10
UE
S2c
* Untrusted non-3GPP access requires ePDG in the data path
UE
Wu*
S2 for connectivity via non-
3GPP acces
Trusted IP access
directly to P-GW
Untrusted IP access via
ePDG
SAE non-3GPP access (23.402)
18
• Deployments are expected to start with overlapping cellular coverage– E-UTRAN overlapping with legacy 3GPP GERAN / UTRAN coverage– E-UTRAN overlapping with legacy 3GPP2 coverage– Multi-mode networks and terminals
• E-UTRAN is a packet-only radio with no CS capacity• Initially E-UTRAN is foreseen as “islands” in the sea of
legacy cellular access– Mobility between E-UTRAN and legacy access is required – Mobility between PS and CS domains is required– Multi-mode terminals expect to use PS coverage where available– Desire to keep the connectivity and services
SAE/LTE Deployment
19
• Continuously Improving Security– EPC requires USIM (or non-3GPP equivalent)
• Multi-mode terminals and networks– Service continuity– Multiple registration– Voice Call Continuity– CS Fallback– Network selection
• Rel 9 will focus on– Regulatory enhancements to LTE/EPC– Home(e) NodeB enhancements to EPC
Other Improvements
20
Summary – The 3GPP Access Onion
GPRSAccess
HSPAAccess
LTEAccess
CDMA2000
Access
WiMaxAccess
NGN (TISPAN)Access
WiFiAccess
CableAccessGPRS
PacketCore
Evolved Packet Core (EPC)
Common IMS
xDSLAccess
Integration of different accesses at different levels
FiberAccess
21
Summary
• LTE is only part of what 3GPP works on• EPC (SAE) is the core network for LTE …
but• IMS and EPC (SAE) can be used to provide
service and session convergence across a variety of accesses
For further information: www.3gpp.org