1 / 47

MUSE Summer School Mobility Management in FMC

MUSE Summer School Mobility Management in FMC. Arkadiusz Sitek June 5 th , 2007. Agenda. Need for mobility management in FMC Standard Internet mobility solutions SIP MIP MUSE mobility management solutions Enhanced SIP-mobility MIP-based mobility Conclusions.

winter-shannon
Download Presentation

MUSE Summer School Mobility Management in FMC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MUSE Summer School Mobility Management in FMC Arkadiusz Sitek June 5th, 2007

  2. Agenda • Need for mobility management in FMC • Standard Internet mobility solutions • SIP • MIP • MUSE mobility management solutions • Enhanced SIP-mobility • MIP-based mobility • Conclusions

  3. Need for mobility management in FMC

  4. FMC • Multiple access networks • WiFi • 3G, 3G/LTE • WiMAX • Wired Ethernet, … • Multiprovider environment • Different parts of network (NAP, RNP, CP, NSP, ASP) possibly managed by independent entities • There are integrated operators on the FMC playground as well • Converged AAA mechanisms • Policy Control and QoS • Mobility Management

  5. Need for mobility management • What services require mobility management? • Real-time services (VoIP, Videotelephony, …) • Streaming services (podcast, vodcast, IP radio, IPTV, …) • Non real-time data services (web browsing, e-mail, IM&P, …) • Solutions • Application layer mobility management • SIP • Network layer mobility management • MIP • No mobility management • Applications designed to work with no session continuity

  6. Flavours of mobility Nomadism: “Ability of the user to change his network access point on moving; when changing the network access point, the user's service session is completely stopped and then started again, i.e., there is no session continuity or handover possible. It is assumed that normal usage pattern is that users shutdown their service session before moving to another access point.” Definition from ETSI/TISPAN Session Continuity: “The ability of a user or terminal to change the network access point while maintaining the ongoing session. This may include a session break and resume, or a certain degree of service interruption or loss of data while changing to the new access point.”. Definition from ETSI/TISPAN. Continuous Mobility: “The ability of a mobile user/terminal/network to change location while media streams are active”. Definition from ITU-T.

  7. Roaming Nomadism Session Continuity Continuous Mobility Handover Seamless Handover Roaming • Roaming: “This is the ability of the users to access services according their user profile while moving outside of their subscribed home network, i.e. by using an access point of a visited network. This requires the ability of the user to get access in the visited network, the existence of an interface between home network and visited network, as well as a roaming agreement between the respective network operators.”. Definition from ETSI/TISPAN. • Roaming requires business (in the first place) agreement between Home and Visited Networks. • Various modes of mobility can be managed during Roaming • Roaming is an orthogonal notion to Nomadism, Session Continuity, Continuous Mobility, …

  8. Standard Internet mobility methods SIP & MIP

  9. Standard SIP mobility • RFC 3261 – re-INVITE • RFC 3515 – REFER • Explicit signalling of IP address, ports, codec changes to the communication peer

  10. Standard SIP mobility summary • Candidate protocol for mobility management in FMC • Need for SIP mobility enhancements

  11. Mobile IP • RFC 3344 & 3024 – MIPv4 & Reverse Tunnelling • RFC 3775 – MIPv6 • Generic network layer mobility management solution • Hide IP address changes from the applications and communications peer • Mobile Node (MN) is always reachable by means of the single Home Address (HoA) • MN uses IP address assigned by the foreign (visited) network to enable IP routing -> Care-of-Address (CoA) • Home Agent (HA) takes care of the the HoA to CoA binding

  12. Flavours of MIP • MIP client implemented in the MN • MN is MIP-aware • MN terminates MIP signalling • MN terminates IP-in-IP tunnel • MIPv4 • MIPv6 • DS-MIPv4 • DS-MIPv6 • MIP client is implemented in the network (Proxy Mobile Agent) • MN is MIP-unaware • MIP signalling terminated at PMA • IP-in-IP tunnel terminated at PMA • PMIPv4 • PMIPv6

  13. MIP summary • Candidate protocol for mobility management in FMC (3GPP standardisation pressure)

  14. Towards continuous mobility – performance comparison • Testbeds: • WLAN <-> WLAN • WLAN <-> GPRS • Real-time services (e.g. VoIP) require handover disruption time to be less that 400ms (ITU-T G.114) • Neither standard SIP nor MIP do assure such behaviour

  15. Mobility Management for FMC SIP-based enhanced mobility

  16. Enhanced SIP mobility • Session Border Controller (SBC) is the solution’s central network element • SBC represents the combination of the P-CSCF and C-BGF IMS functions: • P-CSCF • B2BUA • C-BGF • NAT • RTP proxy • Conferencing module • Key concepts • SIP controlled IP Soft Handover • SBCs Daisy Chaining

  17. SIP controlled IP Soft Handover • Soft handover • Definition: „The service with the target BS starts before disconnection of the service with the previous serving BS” (IEEE Std 802.16e-2005) • During transition from one BS to another, multihomed terminal is simultaneously connected to both BSs. • SBC handles the traffic during handover (conferencing module) • SBC sends duplicated IP traffic downstream via both network interfaces • SBC filters and mixes received upstream IP traffic • Application Service (AS) controls mobility • instructs SBC to activate RTP proxy and conferencing module • Multihomed terminal

  18. SBCs Daisy Chaining • SBCs Daisy Chain • When terminal moves from one network served by one SBC to another network served by different SBC, IP Soft Handover capable SBCs are Daisy Chained to provide continuous mobility • Application Service (AS) controls mobility • Sets up Daisy Chain • IP Soft Handover is kept operational

  19. Enhanced SIP-based mobility for FMC AAA server AAA proxy DHCP server BYE REGISTER INVITE Packager CP1 200 OK ACK Access EN SBC AAA proxy Bob’s home RNP1 NSP1 (Home NSP) NAP1 EN re-INVITE REGISTER BYE Peeringpoint between NSP CP2 AAA server 200 OK AS ACK ASP(single ASP in overlay to NSP) SGSN GGSN RNP2 SBC 3GPP NAP2 NSP2 S-CSCF re-INVITE BYE REGISTER EN AAA server AAA proxy DHCP server 200 OK AAA server Peeringpoint between NSP CP3 ACK Access EN SBC AAA proxy RNP3 Bob’s office NSP3 NAP3 EN AAA server

  20. Enhanced SIP-based mobility summary • Provides mobility to SIP-controlled (IMS) services • Based on standard SIP protocol • Novel access network architecture • Mobility enabler for fixed networks • Interworking with 3GPP possible, but • SIP mobility is not targeted by 3GPP • Advantages: • Privacy Protection • Inter domain continuous mobility (both session and terminal) • Disadvantages: • Network resource utilization is not optimal (more than one SBC involved in the session)

  21. Fixed networks interworking with 3GPP MIP-based mobility

  22. 3GPP FMC view • I-WLAN • Introduced in 3GPP Release 6 • 3GPP subscriber in fixed access network • No session continuity -> nomadic access • WLAN access authentication and authorization through the mobile core network (AAA server, HSS) • I-WLAN Direct IP Access • Access to the IP network (i.e. Internet) directly via WLAN access network • I-WLAN 3GPP IP Access • Utilizes IPSec to establish secure tunnel between MN and 3GPP core network through untrusted access network • Access to the IP network (i.e. Internet) via 3GPP core network • Access to 3GPP PS-based services • QoS assurance

  23. I-WLAN 3GPP Direct IP Access Legend User IP traffic Packager AAA server AAA proxy DHCP server CP1 NSP1 AAA server EN Access EN Bob’s home RNP1 AAA proxy DHCP server NAP1 AN AS GRX Peeringpoint between NSP RNC nodeB I/S-CSCF SGSN HLR/HSS UTRAN/GERAN ASP(single ASP in overlay to NSP) GGSN[PDG] eNodeB NSP2 WAG E-UTRAN AAA server/proxy WLAN BS 3GPP CORE (release 6) GRX NSP1 WLAN Access

  24. I-WLAN 3GPP Direct IP Access • Packet Data Gateway: • IPsec tunnel endpoint • QoS handling • policy enforcement point • IP address management • charging Legend IPSec tunnel User IP traffic Packager AAA server AAA proxy DHCP server CP1 NSP1 I-WLAN PDG EN WAG Access EN AAA server Bob’s home RNP1 AAA proxy DHCP server NAP1 AN • Wireless Access Gateway: • routing to PDG enforcement • QoS handling • charging GRX Peeringpoint between NSP RNC nodeB SGSN HLR/HSS UTRAN/GERAN AS GGSN[I-WLAN PDG] ASP(single ASP in overlay to NSP) eNodeB NSP2 WAG E-UTRAN I/S-CSCF WLAN BS AAA server/proxy 3GPP CORE (release 6) GRX NSP1 WLAN Access

  25. MUSE interworking with 3GPP: session continuity • 3GPP employs SIP solely as a call control protocol • MIP introduced in 3GPP System Architecture Evolution • 3GPP Release 8 • All IP 4G network • fully IP network • simplified network architecture • distributed control • Integration of the non-3GPP access networks • MIP as a session continuity enabler for non-3GPP accesses • 3GPP access to non-3GPP access • non-3GPP access to non-3GPP access

  26. Fixed networks interworking with 3GPP: session continuity • SAE addresses the case where 3GPP subscriber roams in fixed network • 3GPP subscriber in a fixed access network • Case when fixed network subscriber roams in 3GPP access is not covered • MUSE addresses the latter one • Fixed network subscriber in 3GPP access

  27. For non-roaming case VPLMN becomes HPLMN and S2a, S2b, S2c are terminated in PDN GW-v (which becomes PDN GW-h). S8b becomes S5 and can be both GTP and PMIPv6 • Packet Data Network Gateway: • Mobility Anchor between 3GPP and non-3GPP accesses • Mobility Anchor between non-3GPP accesses • MIP HA • Policy Enforcement • Per-user packet filtering (e.g. DPI) • Lawful Intercept • Charging Fixed network – 3GPP rel.8 interworkingMIP-based session continuity – functional view Could be provided by either by fixed operator or 3rd party 3GPP operator that is contracted by HPLFN Wx* Non-3GPPAAA server HSS S2a: PMIPv6 or CMIPv4 FA Co@ S2b: PMIPv6 S2c: DS-MIPv6 or CMIPv4 CCo@ S8b: PMIPv6 Rx+ PCRF-h SGi S7 PDN GW-h • Serving Gateway: • Mobility Anchor for inter-3GPP mobility • Lawful Intercept • Packet routing and forwarding S6a S9 Wd* HPLFN IP service networks(IMS, PSS etc.) Rx+ VPLMN S7 SGi PDN GW-v PCRF-v GERAN S7 S2c S2b S4 MS SGSN S5 S2a S8b 3GPP AAAproxy UTRAN S3 S6d S11 S1-MME Serving GW-v MME S1-U S2b MS EUTRAN S1-U: GTP-U S1-MME: GTP-C+GTP’ S3: GTP S4: GTP S5: GTP S8a: GTP GTP = GTP-U+GTP-C+GTP’ Wm* ePDG-v S2c Wa* S2a Wn* ePDG-v TrustedNon-3GPP IP Access Trusted/UntrustedNon-3GPP IP Access TrustedNon-3GPP IP Access UntrustedNon-3GPP IP Access Can be avoided since MUSE enforces strong and secure authentication and access control Ta* MS

  28. Mobile subscriber in fixed access Relocation to 3GPP EUTRAN rel. 8: PMIPv6 mobility Legend PMIPv6 tunnel GTP-U tunnel User IP traffic Packager AAA server AAA proxy DHCP server CP1 NSP1 EN [PMA] Access EN AAA server Bob’s home RNP1 AAA proxy DHCP server NAP1 AN GRX Peeringpoint between NSP RNC nodeB HSS SGSN MME UTRAN/GERAN AS PDN GW[MIP HA] ASP(single ASP in overlay to NSP) Serving GW[PMA] eNodeB NSP2 E-UTRAN AAA server/proxy I/S-CSCF WLAN BS 3GPP SAE CORE (release 8) GRX NSP1 WLAN Access

  29. Fixed subscriber in 3GPP access Relocation to fixed access: PMIPv6 mobility Legend PMIPv6 tunnel GTP-U tunnel User IP traffic Packager AAA server AAA proxy DHCP server PDN GW [MIPHA, I-WLAN PDG] CP1 NSP1 EN [PMA] Access EN AAA server HSS Bob’s home RNP1 AAA proxy DHCP server NAP1 AN AS GRX Peeringpoint between NSP RNC nodeB HSS I/S-CSCF SGSN MME UTRAN/GERAN ASP(single ASP in overlay to NSP) Serving GW[PMA] eNodeB NSP2 E-UTRAN AAA server/proxy PDN GW[MIP HA] WLAN BS 3GPP SAE CORE (release 8) GRX NSP1 WLAN Access

  30. MIP-based mobility summary • 3GPP Release 6 (I-WLAN) provides nomadic access only • 3GPP Release 8 (SAE) aims session continuity for non-3GPP access networks • PMIPv6 pushed by 3GPP • Network based mobility • Support for non-MIP enabled terminals • Architectural similarities to GTP • SAE architecture is still a „moving target”

  31. Mobility management for FMC summary • Mobility management is the key enabler for FMC • Two approaches: • SIP-based for IMS services • Novel access network architecture (standard SIP protocol) • Mobility enabler for fixed networks • Facilitates integration with IMS • MIP-based for all (including IMS) services • Supported by 3GPP standardization • Facilitates mobility support for legacy terminals (PMIP) • Generic mechanisms for session continuity will increase both terminal and network complexity and entail large investments • It is still to be justified

  32. Backup slides

  33. Legend Authenticator(+ I-WLAN WAG) DHCP Relay PMA (PMIPv6) C-BGF + RTP proxy SIP Client SIP B2BUA RCEF CMIP(v4 or v6)client MIPv4 FA AAA Client 3GPP rel.6/8 entities in MUSE architecture DHCP server AAA server AAA proxy Packager CP1 Private residence MS Service EN Access EN PDN GW [MIPHA, I-WLAN PDG] Mobility Controller RNP1 NSP1 AAA proxy Public WiFi hotspot HSS AAA server AN NAP1 DHCP server EN RNC Peeringpoint between NSP nodeB SGSN Service EN GRX HSS UTRAN/GERAN PDN GW[ePDG, MIP HA] NSP2 MME eNodeB Serving GW MS E-UTRAN AAA server/proxy AS WLAN BS ASP(single ASP in overlay to NSP) 3GPP SAE CORE (release 8) GRX NSP1 WLAN Access I/S-CSCF Peeringpoint between NSP RNC Service EN SGSN nodeB HSS NSP3 GGSN[I-WLAN PDG, PMA, MIP HA] UTRAN/GERAN WAG AAA server/proxy WLAN BS 3GPP CORE (release 6) GRX NSP2 WLAN Access

  34. Legend Authenticator(+ I-WLAN WAG) DHCP Relay PMA (PMIPv4) SIP Client C-BGF + RTP proxy AAA Client CMIP(v4 or v6)client MIPv4 FA RCEF SIP B2BUA WiMAX entities in MUSE architecture AAA proxy AAA server DHCP server Packager CP1 Private residence MS Service EN Access EN PDN GW [MIPHA, I-WLAN PDG] RNP1 Mobility Controller NPM NSP1 AAA proxy Public WiFi hotspot AN NAP1 AAA server DHCP server EN Peeringpoint between NSP AS ASP(single ASP in overlay to NSP) I/S-CSCF Service EN MIPHA ASN-GW RNP2 WiMAX CSN NSP2 MS DHCP server AAA server WiMAX ASN NAP2 WiMAXBS EN

  35. MIPv4 CCoA & Reverse Tunnelling • MN is addressed using both CoA and HoA • MN performs both MIP signalling and user data IP-in-IP tunnelling

  36. MIPv4 FA CoA & Reverse Tunnelling • MN does not know its CoA (it’s managed by Foreign Agent) • MN performs MIP signalling only • FA takes care of user data IP-in-IP tunnelling

  37. MIPv6 • No FA • Route Optimization • MN and CN can communicate directly

  38. Dual Stack MIP • DSMIPv4 • draft-ietf-mip4-dsmipv4-02.txt • Mobility management based on MIPv4 • IPv4 HoA, additionally IPv6 HoA • IPv4 CoA (IPv6 CoA not supported) • Applicable for IPv4 and dual stack access networks • DSMIPv6 • draft-ietf-mip6-nemo-v4traversal-04.txt • Mobility management based on MIPv6 • IPv6 HoA, additionally IPv4 HoA • IPv4 OR IPv6 CoA • Applicable for IPv4, IPv6 and dual stack access networks

  39. Proxy MIP • Host is not aware of mobility • Host does not participate in MIP signalling • Network element performs registration functions on the host’s behalf • Host always obtains its HoA after authentication in PMIP Domain • Host operates as it is always in its home network • PMIPv4 • MIPv4 mobility management • Supports IPv4 and dual stack access networks • PMIPv6 • MIPv6 mobility management • Supports IPv4, IPv6 and dual stack access networks

  40. PMIPv4 • draft-leung-mip4-proxy-mode-02.txt • MS (Mobility Station) • MPA (Mobility Proxy Agent) • Performs MIP signalling on the MS’s behalf

  41. PMIPv6 • draft-ietf-netlmm-proxymip6-01.txt • Proxy Mobile IPv6 Domain (PMIPv6-Domain) • access network where mobility is served using PMIPv6 • Local Mobility Anchor (LMA) • HA in the PMIPv6 domain • Mobile Access Gateway (MAG) • Emulates MN’s Home Network • Proxy Mobile Agent (PMA) • Performs MIP signalling on the MN’s behalf • Located in Mobile Access Gateway (MAG)

  42. S=eNB_IP2@D=sGW_IP1@ UDPhdr GTP-Uhdr S=MS_IP@D=CN_IP@ S=sGW_IP2@D=pGW_IP1@ S=MS_IP@D=CN_IP@ S=EN_IP2@D=pGW_IP1@ UDPhdr S=MS_IP@D=CN_IP@ This is also applicable for 3GPP GERAN or UTRAN (but still with release 8 core). There will be a SGSN (instead of an eNodeB) between MS and Serving GW in that case (ref.point S4 – GTP). Fixed subscriber in 3GPP EUTRAN rel. 8Relocation to fixed access: PMIPv6 mobility Topological anchor for MS_IP@ (Ho@) eNB_IP2@ MS_IP@= Ho@ sGW_IP2@ sGW_IP1@ eNB_IP1@ pGW_IP1@ pGW_IP2@ CP_IP@ S8b SGi S1-U ServingGW PDN GW IP service networks(IMS, PSS etc.) Radiobearer MS eNodeB CN Ho@ PMIPv6 GTP-U IP PMA HA • Home agent in PDN GW will only receive PMIPv6 signalling. • When MS uses 3GPP access (GE-UT-/EUTRAN) GTP will be terminated in serving GW. PMIPv6 is instead used between serving GW and PDN GW (S8b instead of S8a). • Serving GW is informed by MME when it receives the Create Default Bearer Request message that S8b should be used. • MME in turn gets this information during authentication where the HSS of the MS signals that the PDN GW expects PMIPv6. • Since PDN GW is not in 3GPP network, Serving GW needs to interact with PCRF if policies should be obtained. S=MS_IP@D=CN_IP@ S=MS_IP@D=CN_IP@ IPv6 addresses since IPv6 is used in 3GPP core Default gateway for MS VPLMN HPLFN MS_IP@= Ho@ EN_IP2@ EN_IP1@ S8b Accessnode Edgenode Accesslink MS L2Ethernet PMIPv6 PMA IPv6 or IPv4 addresses depending on version used in access S=MS_IP@D=CN_IP@ Legend UDP/IP tunneling if NA(P)T on path (IPv4 case only) Physical NIC Logical NIC (”overloaded on a physical NIC)

  43. S=eNB_IP2@D=sGW_IP1@ UDPhdr GTP-Uhdr S=MS_IP@D=CN_IP@ S=sGW_IP2@D=pGW_IP1@ S=MS_IP@D=CN_IP@ S=EN_IP2@D=pGW_IP1@ UDPhdr S=MS_IP@D=CN_IP@ This is also applicable for 3GPP GERAN or UTRAN (but still with release 8 core). There will be a SGSN (instead of an eNodeB) between MS and Serving GW in that case (ref.point S4 – GTP). Mobile subscriber in fixed accessRelocation to 3GPP EUTRAN rel. 8: PMIPv6 mobility Topological anchor for MS_IP@ (Ho@) eNB_IP2@ MS_IP@= Ho@ sGW_IP2@ sGW_IP1@ eNB_IP1@ pGW_IP1@ pGW_IP2@ CP_IP@ S5 SGi S1-U ServingGW PDN GW IP service networks(IMS, PSS etc.) Radiobearer MS eNodeB CN Ho@ PMIPv6 (or GTP) GTP-U IP PMA HA • Home agent in PDN GW will only receive PMIPv6 signalling. • When MS uses 3GPP access (GE-UT-/EUTRAN) GTP will be terminated in serving GW. PMIPv6 is instead used between serving GW and PDN GW (S8b instead of S8a). • Serving GW is informed by MME when it receives the Create Default Bearer Request message that S8b should be used. • MME in turn gets this information during authentication where the HSS of the MS signals that the PDN GW expects PMIPv6. • Since PDN GW is not in 3GPP network, Serving GW needs to interact with PCRF if policies should be obtained. S=MS_IP@D=CN_IP@ S=MS_IP@D=CN_IP@ IPv6 addresses since IPv6 is used in 3GPP core Default gateway for MS HPLFN VPLMN MS_IP@= Ho@ EN_IP2@ EN_IP1@ S8b Accessnode Edgenode Accesslink MS L2Ethernet PMIPv6 PMA IPv6 or IPv4 addresses depending on version used in access S=MS_IP@D=CN_IP@ Legend UDP/IP tunneling if NA(P)T on path (IPv4 case only) Physical NIC Logical NIC (”overloaded on a physical NIC)

  44. S=eNB_IP2@D=sGW_IP1@ UDPhdr GTP-Uhdr S=MS_IP@D=CN_IP@ S=sGW_IP2@D=pGW_IP1@ S=MS_IP@D=CN_IP@ S=EN_IP2@D=pGW_IP1@ UDPhdr S=MS_IP@D=CN_IP@ This is also applicable for 3GPP GERAN or UTRAN (but still with release 8 core). There will be a SGSN (instead of an eNodeB) between MS and Serving GW in that case (ref.point S4 – GTP). Fixed subscriber in 3GPP EUTRAN rel. 8Relocation to fixed access: MIPv4 with FA Co@ mobility Topological anchor for MS_IP@ (Ho@) eNB_IP2@ MS_IP@= Ho@ sGW_IP2@ sGW_IP1@ eNB_IP1@ pGW_IP1@ pGW_IP2@ CP_IP@ S8b SGi S1-U ServingGW PDN GW IP service networks(IMS, PSS etc.) Radiobearer MS eNodeB CN Ho@ PMIPv6 GTP-U IP MIPv4C PMA HA MS_IP@ • Home agent in PDN GW will receive PMIPv6 signalling when MS uses 3GPP access (EUTRAN) and MIPv4 signalling when MS uses non-3GPP access. • When MS uses 3GPP access (GE-UT-/EUTRAN) GTP will be terminated in serving GW. PMIPv6 is instead used between serving GW and PDN GW (S8b instead of S8a). • Serving GW is informed by MME when it receives the Create Default Bearer Request message that S8b should be used. • MME in turn gets this information during authentication where the HSS of the MS signals that the PDN GW expects PMIPv6. • Since PDN GW is not in 3GPP network, Serving GW need to interact with PCRF if policies should be obtained. • MIPv4C in MS is configured to interpret the IP address assigned to 3GPP LTE NIC as the MIPv4 Ho@. However, the MS will not initiate MIPv4 control signalling on that NIC. S=MS_IP@D=CN_IP@ S=MS_IP@D=CN_IP@ IPv6 addresses since IPv6 is used in 3GPP core Default gateway for MS VPLMN HPLFN MS_IP@= Ho@ EN_IP2@ EN_IP1@ Accessnode Edgenode Accesslink MS L2Ethernet MIPv4 MIPv4C FA MS_IP@ S=MS_IP@D=CN_IP@ UDP/IP tunneling if NA(P)T on path and RFC3519 is supported Legend Physical NIC Logical NIC (”overloaded on a physical NIC)

  45. S=eNB_IP2@D=sGW_IP1@ UDPhdr GTP-Uhdr S=MS_IP@D=CN_IP@ S=sGW_IP2@D=pGW_IP1@ S=MS_IP@D=CN_IP@ S=MS_L_IP@D=pGW_IP1@ UDPhdr S=MS_IP@D=CN_IP@ This is also applicable for 3GPP GERAN or UTRAN (but still with release 8 core). There will be a SGSN (instead of an eNodeB) between MS and Serving GW in that case (ref.point S4 – GTP). Fixed subscriber in 3GPP EUTRAN rel. 8Relocation to fixed access: MIPv4 with CCo@ mobility Topological anchor for MS_IP@ (Ho@) eNB_IP2@ MS_IP@= Ho@ sGW_IP2@ sGW_IP1@ eNB_IP1@ pGW_IP1@ pGW_IP2@ CP_IP@ S8b SGi S1-U ServingGW PDN GW IP service networks(IMS, PSS etc.) Radiobearer MS eNodeB CN Ho@ PMIPv6 GTP-U IP MIPv4C PMA HA MS_IP@ • Home agent in PDN GW will receive PMIPv6 signalling when MS uses 3GPP access (EUTRAN) and MIPv4 signalling when MS uses non-3GPP access. • When MS uses 3GPP access (GE-UT-/EUTRAN) GTP will be terminated in serving GW. PMIPv6 is instead used between serving GW and PDN GW (S8b instead of S8a). • Serving GW is informed that S8b should be used by MME when it receives the Create Default Bearer Request message. • MME in turn gets this information during authentication where the HSS of the MS signals that the PDN GW expects PMIPv6. • Since PDN GW is not in 3GPP network, Serving GW need to interact with PCRF if policies should be obtained. • MIPv4C in MS is configured to interpret the IP address assigned to 3GPP LTE NIC as the MIPv4 Ho@. However, the MS will not initiate MIPv4 control signalling on that NIC. S=MS_IP@D=CN_IP@ S=MS_IP@D=CN_IP@ IPv6 addresses since IPv6 is used in 3GPP core Default gateway for MS VPLMN HPLFN MS_IP@= Ho@ EN_IP1@ Accessnode Edgenode Accesslink MS IP L2Ethernet MIPv4C MS_L_IP@=CCo@ Legend Physical NIC Logical NIC (”overloaded on a physical NIC) UDP/IP tunneling if NA(P)T on path and RFC3519 is supported

  46. S=eNB_IP2@D=sGW_IP1@ UDPhdr GTP-Uhdr S=MS_IP@D=CN_IP@ S=sGW_IP2@D=pGW_IP1@ S=MS_IP@D=CN_IP@ S=MS_L_IP@D=pGW_IP1@ UDPhdr S=MS_IP@D=CN_IP@ This is also applicable for 3GPP GERAN or UTRAN (but still with release 8 core). There will be a SGSN (instead of an eNodeB) between MS and Serving GW in that case (ref.point S4 – GTP). Fixed subscriber in 3GPP EUTRAN rel. 8Relocation to fixed access: DS-MIPv6 mobility Topological anchor for MS_IP@ (Ho@) eNB_IP2@ MS_IP@= Ho@ sGW_IP2@ sGW_IP1@ eNB_IP1@ pGW_IP1@ pGW_IP2@ CP_IP@ S8b SGi S1-U ServingGW PDN GW IP service networks(IMS, PSS etc.) Radiobearer MS eNodeB CN Ho@ PMIPv6 GTP-U IP DS-MIPv6C PMA HA MS_IP@ • Home agent in PDN GW will receive PMIPv6 signalling when MS uses 3GPP access (EUTRAN) and DS-MIPv6 signalling when MS uses non-3GPP access. • When MS uses 3GPP access (GE-UT-/EUTRAN) GTP will be terminated in serving GW. PMIPv6 is instead used between serving GW and PDN GW (S8b instead of S8a). • Serving GW is informed by MME when it receives the Create Default Bearer Request message that S8b should be used. • MME in turn gets this information during authentication where the HSS of the MS signals that the PDN GW expects PMIPv6. • Since PDN GW is not in 3GPP network, Serving GW need to interact with PCRF if policies should be obtained. • DS-MIPv6C in MS is configured to interpret the IP address assigned to 3GPP LTE NIC as the MIPv4/v6 Ho@. However, the MS will not initiate DS-MIPv6 control signalling on that NIC. S=MS_IP@D=CN_IP@ S=MS_IP@D=CN_IP@ IPv6 addresses since IPv6 is used in 3GPP core Default gateway for MS VPLMN HPLFN MS_IP@= Ho@ EN_IP1@ Accessnode Edgenode Accesslink MS IP L2Ethernet DS-MIPv6C MS_L_IP@=CCo@ Legend Physical NIC Logical NIC (”overloaded on a physical NIC) UDP/IP tunneling if NA(P)T on path

  47. S=MS_IP1@D=AN_IP1@ UDPhdr ESPhdr UDPhdr ESPhdr S=MS_IP3@D=HA_IP1@ S=MS_IP2@D=eP_IP1@ UDPhdr S=Ho@D=CN_IP@ TCP/ UDP hdr L7data ESPtrailer ESPtrailer Tunneling frenzy DS-MIPv6, untrusted non-3GPP access & visited anchor in 3GPP DS-MIPv6 tunnel IPSec to tunnel MS into 3GPP core HPLFN Topological anchor for MS_IP2@ Local topological anchor for MS_HoA@ Topological anchor for MS_IP3@ MS_IP1@ MS_IP2@ (IPSec tunnel) MS_IP3@ (IPsec tunnel) MS_Ho@ (MIP tunnel) Serving GW-v Accessnode PDN GW-h MS ePDG-v AN_IP1@ MS_IP2@ HA_IP1@ eP_IP1@ MS_IP3@ MS_Ho@ IPSec tunnel(bootstrapped by PANA) PMIPv6 tunnel Just to demonstrate how complex the tunneling can be. This is the worst case. In practice, the ePDG-v will probably not be there. At least, let’s hope so ... Overhead becomes quite huge. The not so diplomatic comment would be: ARE YOU INSANE?!?! Legend Resulting packet that will leave the MS (UDP headers in dashed boxes only apply if NA(P)T on path Physical NIC Logical NIC (”overloaded on a physical NIC) Indicates to which NIC a logical NIC is tied

More Related