3gpp_Architecture_ev..

1,804 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,804
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
96
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • 1
  • 3gpp_Architecture_ev..

    1. 1. 3GPP presentation Architecture evolution Moscow, October 2008 <ul><li>3GPP TSG CT Chairman </li></ul><ul><li>Hannu Hietalahti </li></ul>
    2. 2. <ul><li>Migration from GSM to multi-access IP multimedia </li></ul><ul><li>From GSM to multi-access </li></ul><ul><li>SIM/USIM/ISIM support </li></ul><ul><li>Security evolution </li></ul><ul><li>System Architecture Evolution (SAE) </li></ul><ul><li>IMS </li></ul><ul><li>Multi-mode terminals and networks </li></ul><ul><ul><li>Service continuity </li></ul></ul><ul><ul><li>Multiple registration </li></ul></ul><ul><ul><li>Voice Call Continuity </li></ul></ul><ul><ul><li>CS Fallback </li></ul></ul><ul><ul><li>Network selection </li></ul></ul>Contents
    3. 3. <ul><li>Continuous improvement of access technologies </li></ul><ul><li>Provision of services over any access network </li></ul>From GSM to multi-access ...and let’s make it IP all the way to the terminal ! Common Core network GSM 900 3G HSPA WLAN E-UTRAN EDGE GSM 1800 GPRS GSM 1900 GSM ph.1 R97 R98 R99 Rel-5/6 Rel-6/7 Rel-8 and onwards WiMAX? ? Fixed Packet Cable
    4. 4. SIM / USIM / ISIM support ??? Rel-8 -> Rel-5 – Rel-7 R99 – Rel-4 GSM Ph.2 – R98 SAE IP Multimedia UMTS 3G phone GSM phone SAE USIM mandatory for SAE access 3G AKA security SIM access not allowed any more No need to update legacy USIM IMC as alternative to ISIM for non-3GPP access IMS Mandatory USIM No SIM specs Optional support of legacy SIM ISIM support mandatory for IMS ME WLAN (Rel-6) <ul><li>WCDMA or EDGE </li></ul><ul><li>Mandatory SIM </li></ul><ul><li>USIM support is: </li></ul><ul><ul><li>Mandatory for WCDMA </li></ul></ul><ul><ul><li>Optional for GSM/EDGE </li></ul></ul>GSM phase 2 Mandatory SIM No USIM support Optional GPRS (R97 ->)
    5. 5. Security evolution Phase 2 SIM 2G AKA SIM SRES Kc RAND RES Ck Ik RES Ck Ik Authentication Request (RAND ) SIP 401 Unauthorised , AUTN GSM security SIM application in UICC 3G AKA in UICC IMS 3G AKA in ISIM +AUTN SIM security in USIM RAND+ AUTN USIM Application 3G AKA ISIM Appl UICC Smartcard, R99 -> 2G AKA RAND RAND SRES Kc 2G AKA SIM Appl SRES Kc RAND 3G AKA
    6. 6. <ul><li>LTE = E-UTRAN = evolved radio network </li></ul><ul><ul><li>Megabit class data rates </li></ul></ul><ul><ul><li>Short delays </li></ul></ul><ul><ul><li>Short transition from idle to active </li></ul></ul><ul><li>SAE = System Architecture evolution </li></ul><ul><ul><li>Evolved IP oriented multi access architecture </li></ul></ul><ul><li>E-UTRAN integrates only to SAE, A/Gb or Iu not possible </li></ul><ul><li>Strongly IP based PS only network </li></ul><ul><li>SAE covers both 3GPP and non-3GPP access technologies </li></ul><ul><li>Seamless roaming between E-UTRAN, 2G and 3G (tight interworking) </li></ul><ul><li>Loose interworking with non-3GPP accesses </li></ul><ul><li>Currently work is progressing on GTP for intra-3GPP mobility and IETF based mobility for non-3GPP mobility </li></ul><ul><ul><li>The main Architecture specifications 23.401 and 23.402 frozen in June 2008 </li></ul></ul><ul><ul><li>Protocol work is ongoing with the goal to freeze it in December 2008 </li></ul></ul>System Architecture Evolution (SAE)
    7. 7. <ul><li>Deployments are expected to start with overlapping cellular coverage </li></ul><ul><ul><li>E-UTRAN overlapping with legacy 3GPP GERAN / UTRAN coverage </li></ul></ul><ul><ul><li>E-UTRAN overlapping with legacy 3GPP2 coverage </li></ul></ul><ul><ul><li>Multi-mode networks and terminals </li></ul></ul><ul><li>E-UTRAN is a packet-only radio with no CS capacity </li></ul><ul><li>Initially E-UTRAN is foreseen as “islands” in the sea of legacy cellular access </li></ul><ul><ul><li>Mobility between E-UTRAN and legacy access is required </li></ul></ul><ul><ul><li>Mobility between PS and CS domains is required </li></ul></ul><ul><ul><li>Multi-mode terminals expect to use PS coverage where available </li></ul></ul><ul><ul><li>Desire to keep the connectivity and services </li></ul></ul>SAE/LTE Deployment
    8. 8. IP Multimedia Subsystem (IMS) <ul><li>PS domain IP Multimedia service platform </li></ul><ul><li>Based on open IETF standards </li></ul><ul><ul><li>End to end IP (SIP) </li></ul></ul><ul><ul><li>Multi access </li></ul></ul><ul><ul><ul><li>GPRS, I-WLAN, fixed xDSL, Packet Cable defined </li></ul></ul></ul><ul><ul><ul><li>More access technologies to follow... </li></ul></ul></ul>Internet Circuit-switched network (2G or 3G) PSTN IP connectivity (GPRS, 3G,...) Find & route to destination User data Any IP connectivity (3G, WLAN,...) End-to-End IP services IP Multimedia Core
    9. 9. <ul><li>3GPP members, 3GPP2, WiMAX forum, ETSI TISPAN and CableLabs contribute to 3GPP common IMS specifications </li></ul><ul><ul><li>Different requirements are supported in common implementation </li></ul></ul><ul><li>All IMS specifications are harmonized to 3GPP specifications </li></ul><ul><ul><li>Common parts are defined in 3GPP specifications only </li></ul></ul><ul><ul><ul><li>Core IMS entities (CSCFs, AS, UE IMS client,...) + agreed common functions </li></ul></ul></ul><ul><ul><li>Other organisations either reference or re-use 3GPP specification as it stands </li></ul></ul><ul><ul><li>Any changes or additions in the Common IMS area are made in 3GPP </li></ul></ul><ul><ul><ul><li>All 3GPP members can contribute on their favourite work items </li></ul></ul></ul><ul><ul><ul><li>Ongoing work initiated by 3GPP members, CableLabs, 3GPP2 and ETSI TISPAN </li></ul></ul></ul><ul><ul><li>The scope and coverage of Common IMS have been agreed by the SDOs </li></ul></ul><ul><li>Common version of IMS specifications in Rel-8 </li></ul><ul><ul><li>Business or architecture specific additions to 3GPP Common IMS are possible outside the agreed Common IMS area </li></ul></ul>Common IMS
    10. 10. <ul><li>Call control protocols </li></ul><ul><ul><li>E-UTRAN is a PS only radio, speech and other services are IMS based </li></ul></ul><ul><ul><li>PS domain IMS uses SIP protocol for call control (3GPP TS 24.229) </li></ul></ul><ul><ul><li>CS domain uses Call Control defined in 3GPP TS 24.008 </li></ul></ul><ul><li>Voice Call Continuity </li></ul><ul><ul><li>Domain transfer of ongoing call </li></ul></ul><ul><ul><li>Typically from E-UTRAN to 2G or 3G access </li></ul></ul><ul><li>CS fallback </li></ul><ul><ul><li>Paging the mobile in E-UTRAN to start CS service in 2G or 3G access </li></ul></ul><ul><ul><li>Not an E-UTRAN service, but fallback to existing service via 2G/3G </li></ul></ul><ul><li>IMS service continuity </li></ul><ul><ul><li>IMS service between E-UTRAN and other PS only, such as WLAN </li></ul></ul><ul><li>IMS Centralized Service Control (ICS) </li></ul><ul><ul><li>Common telephony services between CS and PS domain </li></ul></ul>Multi-mode, Service continuity
    11. 11. Multi-mode, IMS registration in Rel-7 <ul><li>When S-CSCF detects that the same UE registers again, it considers this as an update and overwrites existing registration </li></ul><ul><li>In some cases it may not be possible to de-register when changing from one access technology to another </li></ul><ul><ul><li>UE might lose radio coverage before being able to de-register </li></ul></ul><ul><li>S-CSCF detects that the registration is from the same UE based on the same privateID, which is practically a device-ID </li></ul>UE (privateID-A) S-CSCF REGISTER 1 (privateID-A, IPaddress: 1.2.3.4) loss of radio UE registered with 1.2.3.4 REGISTER 2 (privateID-A, IPaddress: a.b.c.d) UE registered ONLY with a.b.c.d – REGISTER 1 got overwritten with REGISTER 2
    12. 12. Multi-mode, IMS Multiple registration, Rel-8 <ul><li>A UE is able to register the same public user identity with multiple IP addresses at the same time </li></ul><ul><li>Used e.g. for IMS Service Continuity (e.g. handing over from I-WLAN to GPRS) </li></ul><ul><li>No gap in reachability of the mobile </li></ul>S-CSCF P-CSCF 1 P-CSCF 2 GPRS IP: 1.2.3.4 UE-A HSS I-WLAN IP: a.b.c.d user1 / 1.2.3.4 / UE-A user1 / a.b.c.d / UE-A
    13. 13. Multi-mode, Single Radio Voice Call Continuity Transfer from E-UTRAN to GERAN with active call (not all entities shown) PLMN serving remote user MSC server IMS MSC E-UTRAN 2G or 3G measurements HO required MME relocation request prepare HO relocation response session transfer HO command HO complete
    14. 14. Multi-mode, CS fallback Directing the UE from E-UTRAN to 2G/3G for CS service PLMN serving remote user MSC E-UTRAN 2G or 3G MME SETUP call setup paging paging paging resp. SETUP
    15. 15. Multi-mode, Network selection <ul><li>Network selection comprises two parts </li></ul><ul><ul><li>Network operator selection (the goal, based on commercial agreement) </li></ul></ul><ul><ul><ul><li>Home operator determines which visited operators are preferred </li></ul></ul></ul><ul><ul><li>Access technology selection (the means, based on technical criteria) </li></ul></ul><ul><ul><ul><li>Serving visited operator determines access technology, frequency band and cell </li></ul></ul></ul><ul><li>Multi-mode phones supporting many access technologies are a new challenge </li></ul><ul><li>Network selection within each technology is defined for 3GPP and non-3GPP accesses </li></ul><ul><li>The combination of multiple technologies is undefined </li></ul><ul><li>Two approaches are foreseen in Rel-8 </li></ul><ul><ul><li>3GPP network selection procedures are extended to cover any non-3GPP system that supports ITU-T defined concepts of MCC and MNC </li></ul></ul><ul><ul><li>For others the ANDSF can (optionally) download network selection policy </li></ul></ul><ul><ul><ul><li>Access technology preference, policy for changing access technology, etc. </li></ul></ul></ul><ul><li>MCC = Mobile Country Code </li></ul><ul><li>MNC = Mobile Network Code </li></ul><ul><li>ANDSF = Access Network Discovery and Selection Function </li></ul>
    16. 16. Multi-mode network selection, Outbound roaming example PLMN Selector (USIM): VPLMN5 VPLMN2 VPLMN1 HPLMN VPLMN1 VPLMN2 VPLMN1 CDMA VPLMN2 GERAN VPLMN1 E-UTRAN ? HPLMN has not configured RAT priority for this VPLMN <ul><li>HPLMN is not available </li></ul><ul><li>Prioritized VPLMNs are listed with no associated RAT in PLMN selector with access technology: </li></ul><ul><ul><li>VPLMN5 is not available </li></ul></ul><ul><ul><li>VPLMN1 is available </li></ul></ul><ul><ul><li>VPLMN2 is available </li></ul></ul><ul><li>VPLMN2 is selected via 2G, 3G or E-UTRAN </li></ul><ul><ul><li>USIM configured RAT preference possible </li></ul></ul><ul><li>After PLMN selection normal idle mode is resumed </li></ul><ul><ul><li>Cell & RAT may change within the selected PLMN </li></ul></ul><ul><ul><li>Background scan for higher priority network </li></ul></ul>RAT = Radio Access Technology, PLMN = Public Land Mobile Network VPLMN2 UTRAN VPLMN2 E-UTRAN
    17. 17. Thanks for your attention ! More information at www.3gpp.org
    18. 18. Architecture Annex: 3GPP and non-3GPP access architecture
    19. 19. SAE architecture (23.401) 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 User plane security (UMTS AKA) Signaling security (UMTS AKA)
    20. 20. SAE non-3GPP access (23.402) S2 for connectivity via non-3GPP acces Trusted IP access directly to P-GW Untrusted IP access via ePDG 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 S5 S6c Rx+ Rx+ S2a PDN Gateway MME S11 S10 UE S2c * Untrusted non-3GPP access requires ePDG in the data path UE Wu*

    ×