IP Mobility Management
Youn-Hee Han Korea University of Technology and Education Laboratory of Intelligent Networks 2009 Outline IP Mobility - Why and What Mobile IPv4/IPv6 (RFC 3344/3775)
IP Handover Optimization Network-based Mobility Support Network-based Mobility Optimization & Future Research Issues IP Mobility - Why and What IPs Routing Model Internet
Router Internet Router Addresses are assigned in a topologically significant manner Routing based on address prefixes MN(Mobile Node) must be assigned a new address when it moves IP Session Continuity Internet TCP connections are defined by
Router Internet Router TCP connections are defined by [Source IP, Source Port, Destination IP, Destination Port] MNs address must be preserved regardless of its location to preserve the on-going IP session. Therefore, when an MN moves, Retain the MN address Routing fails Change the MN address IP Session breaks Solutions : Two-tier IP addressing
Router Internet Router MN keeps its static IP address, but uses a temporary a CoA(care-of address) when it moves to another subnet HoA (Home Address) the original static IP address CoA (Care-of Address) the temporary IP address Why Network-layer Mobility?
Transport Layer/ Application Layer transparency Mobility management is related with addressing Why IP Mobility? IP Mobility ?
Session Application IP Mobility Path Extension . Host-based routing Session IP Address Session IP Address WiBro IP Mobility , Session IP Mobility . IP Cloudfor L 2 Mobility Backbone Network Micro Mobility Zone Subnet - 1 Routing RAS3 RAS1 RAS2 L p a t h E x e n d MSS ACR ( Anchor ) Why IP Mobility? IP Mobility ?
Peer-to-Peer IP Mobility IP Session ? The world of IPv6 DRINK Mobile telephone Image Server Music Data car Map information Vending machines Data-compatible home appliances Broadcasting Settlement \ IPv VHO and IP Mobility IP Access Network
Horizontal Handover using one interface Intra-cell Handover - Inter-cell Handover Inter-PHY/MAC Attachment Points - Inter-PHY/MAC Attachment Points/Layer 3 Network - Vertical Handover using multi-interfaces Inter-cell (Heterogeneous Cell) Handover Inter-PHY/MAC Attachment Points - Inter-PHY/MAC Attachment Points/Layer 3 Network - 802.16/WiBro 802.11/WLAN HSDPA IP Access Network Handover requiring IP handover : 802.16 HSDPA (or LTE) 802.16 802.16 802.11 IP address and VHO Session Continuity
Conflict Relation in VHO IP session continuity implies IP address preservation. Multi-interfaces configures its individual IP address. IP Mobility resolves the conflict!!! Two-tier IP Addressing strategy resolves the conflict For session continuity, HoA is used. For temporal locator, CoA is used at each interface. A new CoA (not HoA) is configured to terminals new interface after movement Each interface configures and manages its own CoA Mobile IPv4/IPv6 (RFC 3344/3775) Mobile IPv4 IETF Standard Documents Major Component
RFC 3344 (IP Mobility Support for IPv4), Aug. 2002 draft-ietf-mip4-rfc3344bis-07.txt (IP Mobility Support for IPv4, revised), Oct. 2008 Major Component HA Home Agent FA Foreign Agent (usually in Router) MN Mobile Node New Signal Message related with Registration Management Agent Discovery Agent Solicitation/Agent Advertisement (ICMP Messages) It makes use of the existing Router Advertisement/Solicitation messages defined for ICMP Router Discovery (RFC 1256). Registration Registration Request/Registration Reply (UDP Messages) Mobile IPv4 Operation Mobile IPv4 Operation
CN MN Basic Operation of Mobile IPv4 Payload SRC: CNs Addr. DEST: MNs HoA DEST: CNs Addr. SRC: MNs HoA Payload CN CN MN 0) MN in Home Network MN has only HoA Normal routing 1) Agent Solicitation (ICMP) 2) Agent Advertisement (ICMP) MN in Foreign Network 3) MN obtains a new CoA (FA-CoA) move Mobile IPv4 Operation Mobile IPv4 Operation
Basic Operation of Mobile IPv4 CN Registration Table 2) Registration Request (UDP) HoA CoA Normal routing 3) Registration Reply (UDP) 1) Registration Request (UDP) 4) Registration Reply (UDP) Mobile IPv4 Operation Mobile IPv4 Operation
Basic Operation of Mobile IPv4 CN (HA) Payload SRC: CNs Addr. DEST: MNs HoA CN Registration Table HoA CoA (FA) (HA) DEST: MNs CoA SRC:HAs Addr DEST:MNs HoA SRC:CNs Addr. Payload (FA) MN Payload SRC: CNs Addr. DEST: MNs HoA Mobile IPv4 Operation Mobile IPv4 Operation
Basic Operation of Mobile IPv4 CN Registration Table HoA CoA DEST: CNs Addr. SRC: MNs HoA Payload CN MN Mobile IPv4 Features Triangle Routing Two CoA Modes
CN HA MN,MN CN It deteriorates service of quality MIP4 Route optimization Not yet standardized Some research-level papers Two CoA Modes FA-CoA MNs receive a CoA from FA No duplication about new CoA Co-located CoA DHCP-based CoA allocation DHCP server should guarantee the uniqueness of CoA FA-CoA is preferred because of the depletion of the IPv4 address space IPv6 Why IPv6? Why IPv6 and Mobile IPv6 Infinite Address Space
128 bits address Autoconfiguration Service IP address auto-configuration without DHCP Efficient Routing Managed prefix allocation The number of routing entry will be reduced at routers Perfect peer-to-peering Built-in Security Efficient Mobility Mobile IPv6 Why IPv6 and Mobile IPv6
RFC 3775, Mobility Support in IPv6, June 2004 D. Johnson (Rice Univ.), C. Perkins (Nokia), J. Arkko (Ericsson) It takes almost 4 years to make it RFC. draft-ietf-mext-rfc3775bis-03.txt (March 9, 2009) Major Components HA MN (no FA) From implementations viewpoint MIPv6 is a pure network-layer protocol, while MIPv4 is an application and network-layer protocol. New Message and Options of Mobile IPv6
Why IPv6 and Mobile IPv6 New Message and Options of Mobile IPv6 New Signal Message related with Binging Management Binding Update (BU) Binding Acknowledgement (BAck) Binding Refresh Request (BRR) Binding Error (BE) New Signal Message related with Binding Authentication Home Test Init (HoTI) Care-of Test Init (CoTI) Home Test (HoT) Care-of Test (CoT) New Destination Option Home Address Destination Option New Routing Header Type Routing Header Type 2 Mobile IPv6 Operation MN at Home Network Move Movement Detection
CN MN CN Payload SRC: CNs Addr. DEST: MNs HoA DEST: CNs Addr. SRC: MNs HoA Payload CN MN Internet Home N/W Foreign N/W AR AR HA RouterSolicitation after link-up trigger RouterAdvertisement 0) MN at Home NetworkMN gets HoA (Home Address) 1) MN gets Router Advertisement message 2) MN detects its Layer 3 Movements Mobile IPv6 Operation Location Registration Internet Binding Cache CN
HoA CoA Internet Home N/W Foreign N/W 4) MN sends a BU AR AR HA 5) HA acknowledges by returning BAck to MN 6) HA setups Proxy Neighbor Cache for intercepting packets destined for MN 3) MN configures New CoA after executingDuplicate Address Detection (DAD) Mobile IPv6 Operation Packet Tunneling Internet (HA) MN CN CN (HA)
Payload SRC:CNs Addr. DEST:MNs HoA SRC:HAs Addr DEST: MNs CoA CN CN (HA) DEST: HAs Addr. SRC: MNs CoA DEST: CNs Addr. MNs HoA Payload Payload SRC: CNs Addr. DEST: MNs HoA (HA) MN DEST: CNs Addr. SRC: MNs HoA Payload CN (HA) Internet Home N/W Foreign N/W AR AR HA MN 7) HA intercepts packets with HoA as its destination address 9) Decapsulatethe packet 8) HA sends encapsulated packets to MNs CoA inbound MN MN Payload SRC: CNs Addr. DEST: MNs HoA 10) Looping Back DEST: CNs Addr. SRC: MNs HoA Payload MN MN outbound Mobile IPv6 Operation Return Routability with CN Internet
5) CN generates binding management key CN 4) MN sends CoTI to CN directly Internet Home N/W Foreign N/W AR AR HA 3) MN sends HoTI to CN via HA MN 1) MN guesses that the CN has no Binding Cache for me 2) MN executes Return Routability Mobile IPv6 Operation Return Routability with CN Internet
Binding Cache 10) MN sends BU with binding authorization data 11) CN need not return BAck CN HoA CoA 7) CN sends CoT to MN directly Internet Home N/W Foreign N/W AR AR HA 6) CN sends HoT to MN via HA MN 8) MN generates binding management key 9) MN computes binding authorization data (signature) for BU message Routing Header (MNs HoA) Home Addr. Dest. Opt. (MNs HoA)
Mobile IPv6 Operation Route optimization after BU with CN CN 12) CN directly sends packets to MNs CoA by using Routing header type 2 CN MN Payload Routing Header (MNs HoA) SRC: CNs Addr. DEST: MNs CoA Internet Home N/W Foreign N/W AR AR HA MN 13) MN directly sends packets to CN by using Home Address Destination option CN MN DEST: CNs Addr. SRC: MNs COA Home Addr. Dest. Opt. (MNs HoA) Payload Mobile IPv6 Operation Why IPv6 and Mobile IPv6
When the bindings lifetime of CN is near expiration 1) CN guesses that it is activelycommunicating with the MN andhas indications, such as an open TCP connection to the MN 2) CN sends a BRR to the MN CN Internet Home N/W Foreign N/W AR AR HA MN 3) MN replies by returning a BU to the CN Mobile IPv6 Features Why IPv6 and Mobile IPv6 How to make CoA?
Auto-configuration Without DHCP (Preferred) With DHCP Duplication Address Detection (DAD) is required. Triangle routing avoided, but non-optimal routing is default Route optimization supported But, CN is required to be modified for the route optimization Security MN HA : Strong Security (IPSec) MN CN : Weak Security (Return Routability) Handover latency increased Handover Latency of Mobile IPv6
Why IPv6 and Mobile IPv6 Handover Latency of Mobile IPv6 L2 handover MD DAD RR & BU Standard MIPv6 (Reactive) time Up to about 2.5 seconds Latency Components MD (Movement Detection) Latency How to get Router Advertisement fast? DAD (Duplicate Address Detection) Latency Constant time (1 sec.) How to shorten the constant time? BU (Binding Update) Latency It depends on the distance between MN and HA/CN Mobile IPv6 is not a handover protocol, rather it is a location (and route) update and session continuity protocol. IP Handover Optimization Optimization of Each Phase
IP Handover (1/3) Movement Detection (MD) Latency Fast Router Advertisement(FRA) draft-mkhalil-ipv6-fastra-05.txt Fast Router Discovery(FRD) draft-ietf-dna-frd-02.txt [FRA] Link-specific Handover& AAA AR AP/BS MN RS RA MN receives RA & discovers new subnet. Link-specific Handover& AAA Link-Up & Layer 3 (and above) Communication Ready How Long? AR AP/BS MN RA [FRD] AR AP/BS MN Link-specific Handover& AAA RA Optimization of Each Phase
IP Handover (2/3) DAD Latency Optimistic Duplicate Address Detection (oDAD) RFC 4429 (Aprial, 2006) Advance Duplicate Address Detection (aDAD) Y.-H. Han and S.-H. Hwang, "Care-of Address Provisioning for Efficient IPv6 Mobility Support", Elsevier Computer Communications, Vol.29, No.9, pp , 2006. AR AP/BS RS RA NS BU to Home Agent Link-specific Handover& AAA MN Link-Up MN receives RA Timeout (1 sec.) [oDAD aDAD DAD ] Optimization of Each Phase
IP Handover (3/3) Binding Update Latency Hierarchical Mobile IPv6 (HMIPv6) - RFC 4140 (August, 2005) [Standard MIPv6 (RFC 3775)] [Optimized MIPv6] MD Optimization RS+RA (RFC 3775 Optional) FRA (IETF Proposal), FRD (IETF Proposal) DAD Optimization oDAD (RFC 4429) aDAD (A paper, IETF Proposal) BU Optimization HMIPv6 (RFC 4140) L2 handover MD DAD BU time Layer 2+3 Latency L2 handover MD+DAD+BU time Layer 2+3 Latency Optimization of The Whole Procedure
IP Handover (1/3) Fast Handovers for Mobile IPv6 (FMIPv6) - RFC 4068 (July 2005) Predictive (Preferred) & Reactive MD DAD Layer 2 MN PAR NAR L2 trigger RtSolPr PrRtAdv FBU HI HACK FBACK FBACK New 4 ICMPv6 Messages - Router Solicitation for Proxy (RtSolPr) - Proxy Router Advertisement (PrRtAdv) - Handover Initiate (HI) Handover Acknowledge (HACK) New 3 Mobility Messages - Fast Binding Update (FBU) - Fast Binding Acknowledgment (FBACK) - Fast Neighbor Advertisement (FNA) Disconnect forward packets Connect FNA deliver packets Optimization of The Whole Procedure
IP Handover (2/3) Fast Handovers for Mobile IPv6 (FMIPv6) - RFC 4068 (July 2005) Layer 2 Mobile IPv6 Fast Handovers for Networks - RFC 4260 (Nov. 2005) Mobile IPv6 Fast Handovers over IEEE e Networks - RFC 5270 (June 2008) Mobile IPv6 Fast Handovers for 3G CDMA Networks - RFC 5271 (June 2008) Layer 3 (FMIPv6) Cross-layering Layer 2 (WiMAX/WiBro) Optimization of The Whole Procedure
IP Handover (3/3) Fast Reactive Scheme Y.-H. Han, J.-H. Choi, and S.-H. Hwang, "Reactive Handover Optimization in IPv6-Based Mobile Networks," IEEE JSAC, pp , September 2006 Combined MD and DAD AR sends a unicast RAmessage with a unique CoA directly to MN when the MNmakes a connection with a new AP. Network-based BU Handover Latency Comparison
L2 handover MD DAD BU [Standard MIPv6 (RFC 3775)] [Optimized MIPv6] [Fast Reactive Handover Opti.] [FMIPv6] time Layer 2+3 Latency L2 handover Optimized MD, DAD, and BU time Layer 2+3 Latency L2 handover Combined MD&DAD + Network-based BU time Layer 2+3 Latency RtSolPr PrRtAdv FBU, HI, HAck, FBAck MD BU+DAD Tunneling FNA time Layer 2+3 Latency Network-based Mobility Support Proxy Mobile IPv6 Proxy Mobile IPv6 [IETF RFC 5213, August 2008] LMA
LMA: Localized Mobility Agent MAG: Mobile Access Gateway IP Tunnel IP-in-IP tunnel between LMA and MAG LMA Home Network MNs Home Network (Topological Anchor Point) MAG LMA Address (LMAA) That will be the tunnel entry-point LMM(Localized Mobility Management) Domain MAG movement Proxy Binding Update/Ack. (PBU/PBA) Control messages exchanged by MAG to LMA to establish a binding between MN-HoA and Proxy-CoA MNs Home Network Prefix (MN-HNP) CAFE:2:/64 MN Home Address (MN-HoA) MN continues to use it as long asit roams within a same domain Proxy Care of Address (Proxy-CoA) The address of MAGThat will be the tunnel end-point PMIPv6 Operation Flow MN MAG AAA&Policy Store LMA CN DHCP Server
PBU: Proxy Binding Update PBA: Proxy Binding Ack. RA*: MN Prefix Policy Store Router Advertisement RA**: MN Prefix LMA Router Advertisement MN MAG AAA&Policy Store LMA CN MN Attachment AAA Query with MN-ID AAA Reply with Profile RA* PBU with MN-ID, Home Network Prefix option, Timestamp option PBA with MN-ID, Home Network Prefix option RA** Tunnel Setup Optional DHCP Server DHCP Request DHCP Request DHCP Response DHCP Response [MN-HoA:CN](data) [Proxy-CoA:LMAA][MN-HoA:CN](data) [MN-HoA:CN](data) PMIPv6 Features Home in Any Place RA Unicast
MAG sends the RA (Router Advertisement) messages advertising MNs home network prefix and other parameters MAG will emulate the home link on its access link. RA Unicast RA should be UNICASTed to an MN It will contain MNs Home Network Prefix Per-MN Prefix Any MN is just a IPv6 host Any MN is just a IPv6 host with its protocol operation consistent with the base IPv6 specification. M:1 Tunnel LMA-MAG tunnel is a shared tunnel among many MNs. One tunnel is associated to multiple MNs Binding Caches. PMIPv6 over WiMAX/WiBro
Proxy Mobile IPv6 over WiBro IP Network Internet E R ACR/MAG L2 Switch BS/RAS PSS HA or LMA AAA/Policy Store ACR DNS NMS TTA , IPv6 , TTAK.KO , Dec. 2008 Previous MAG Previous MAG PMIPv6 in 3GPP LTE/EPC Proxy Mobile IPv6 over LTE
AAA/ Policy Server Ref.] I. Guardini et al., Mobile IPv6 deployment opportunities in next generation 3GPP networks, 16th IST Mobile&Wireless Communication Summit, Budapest, Hungary 1-5, July 2007 GTP-U Tunnel IP-in-IP Tunnel UE eNodeB S-GW/(MAG) P-GW/LMA P-GW: access gateway towards Packet Data Networks (similar to the GGSN) Optional! - PMIPv6 will be mainly used for inter-system handovers(i.e. handovers between 3GPP and non-3GPP accesses) PMIPv6 in 3GPP LTE/EPC Proxy Mobile IPv6 over LTE
Vertical handover scenario LMA LMA DS(Dual Stack)-PMIPv6 Standard Documents
IPv4 Support for Proxy Mobile IPv6 (DS-PMIPv6) draft-ietf-netlmm-pmip6-ipv4-support-12.txt (April 2009) IPv4 Transport + IPv4 Home Address Mobility DS-PMIPv6 Cellular IP network WLAN IP Network WiBro IP Network RAS LTE BS WLAN AP IPv4 IPv6 Private IPv4 NAT AAA DSMIPv6 HA IPv4 Application (VoD, IP-Phone) IPv6 Application (VoD, IP-Phone) DSMIPv6 MN DS(Dual Stack)-PMIPv6 PMIPv6s Dual-Stack Support
[Mobility Binding] HoAv4 and HoAv6 Dual Stack MN orIPv4 MN PBU (HoAv6, Proxy CoAv6, HoAv4) Proxy CoAv6 IPv4 traffic CNv4 HoAv4 IPv6 Tunnel (LMAAv6Proxy CoAv6) IPv6 traffic CNv6->HoAv6 Dual Stack MAG Only-IPv6 enabled (Proxy CoAv6) Dual Stack LMA Only-IPv6 enabled (LMMAv6) [Mobility Binding] HoAv4 and HoAv6 Dual Stack MN orIPv4 MN PBU (HoAv6, Proxy CoAv4, HoAv4) Proxy CoAv4 IPv4 traffic CNv4 HoAv4 IPv4 Tunnel (LMAAv4Proxy CoAv4) IPv6 traffic CNv6->HoAv6 Dual Stack MAG Only-IPv4 enabled (Proxy CoAv4) Dual Stack LMA Only-IPv4 enabled (LMAAv4) DS(Dual Stack)-PMIPv6 MAG LMA LMA ( : IPv6 HoA & IPv4 HoA IPv4 or IPv6 Proxy-CoA ) IPv4-UDP-IPv6-PBU IPv4-UDP-IPv6-PBU IPv6-PBU IPv6-PBAck IPv4-UDP-IPv6-PBAck IPv4-UDP-IPv6-PBAck NAT 6-in-6 Tunnel 4-in-6 Tunnel 6-in-4 Tunnel 4-in-4 Tunnel 6-in-udp-in-4 Tunnel 4-in-udp-in-4 Tunnel MAG MAG MAG MN IPv6 MN IPv4 MN Private IPv4 LMA MN Prefix Pool
DS-PMIPv6 -1 v4/v6 VoD Server CN ETRI (2007,2008) eth1) 3ffe:2::1/64 LMA MN has Dual Stack and both addresses are always enabled V4/V6 network eth0) 3ffe:2::2/64 LMA MN Prefix Pool 3ffe:1:3:1::/64 ~ 3ffe:1:3:ffff::/64 eth0) 3ffe:1::1/64 NAT Private V4 network V6 network eth0) V4 network MAG3 eth0) 3ffe:1::2/64 MAG1 eth0) MAG2 ra0) 3ffe:1:3::1/64 fe80::1 ra0) 3ffe:1:1::1/64 fe80::1 ra0) 3ffe:1:2::1/64 fe80::1 SSID: PMIP3 SSID: PMIP1 SSID: PMIP2 : v4 VoD Client : v6 VoD Client DS-PMIPv6 -2 KT (2007): DS-PMIPv6 with Only Private IPv4 Network and IPv4 Application LMA (PC0) VoD (PC4) Subnet 4 NAT1 NAT2 MAG1 (PC1) MAG2 (PC2) Subnet 1 Subnet 2 MAG3 (PC3) Subnet 3 Notebook1 Notebook2 802.11g 802.11a Network-based Mobility Optimization & Future Research Issues Network-based Handover Optimization
IP Handover Basic Standard Proxy Mobile IPv6 (PMIPv6) RFC 5213 (Aug. 2008) Base Protocol IETF Fast Handovers for Proxy Mobile IPv6 (F-PMIPv6) draft-ietf-mipshop-pfmipv6-04.txt (May 2009) Transient Binding for Proxy Mobile IPv6 (TB-PMIPv6) draft-ietf-mipshop-transient-bce-pmipv6-02.txt (March 2009) Make-before-break L2 handover MD (), DAD (), Network-based BU [PMIPv6] time Layer 2+3 Latency Fast Handover for PMIPv6
F-PMIPv6 Procedure Access technology specific (out of scope) (Tunnel Setup) NAR requests PAR toforward or buffer the packets & Tunnel Setup(When? out of scope) Forwarding (Buffering at NAR) Access technology specific (out of scope) Fast Handover for PMIPv6
Cross-layering E.g.,) F-PMIPv6 over WiMAX/WiBro Report(MN ID, BS3) Predictive Handover Fast Handover for PMIPv6
PMIPv6 vs. F-PMIPv6 HO-INITIATE HO-COMPLETE (Link-UP) Link-specificHandover MN PBU PBAck LMA Old MAG New MAG Total Handover Latency PMIPv6 Link-specificHandover MN PBU PBAck LMA Old MAG New MAG Total Handover Latency HI HAck Buffering F-PMIPv6 HO-INITIATE HO-COMPLETE (Link-UP) Transient Binding for PMIPv6
Problem Description of PMIPv6 at VHO Occurs at the make-before-break L2 handover No Way! Uplink packets HNP MN-ID CoA ATT MN-LL-ID HNP#1 MN Proxy-CoA1 5 XXX HNP MN-ID CoA ATT MN-LL-ID HNP#1 MN Proxy-CoA2 5 XXX LMA LMA Uplink packets PBU(Proxy-CoA1) PBA (HNP=HNP#1) PBA (HNP=HNP#1) PBU(Proxy-CoA2) MAG MAG MAG MAG Downlink packets Packet Loss! WiBro WiBro WiBro WiBro RA (Prefix=HNP#1) RA (Prefix=HNP#1) Downlink packets HNP#1 HNP#1 WiBro (IEEE 802 MAC: XXX) WiBro (IEEE 802 MAC: XXX) MN MN The network nodes may prematurely move MNs binding to the new access even while the MN is sending outgoing packets onto the old access. Transient Binding for PMIPv6
Proposed Procedure Current BCE HNP MN-ID CoA ATT MN-LL-ID state Forwarding allowed 1 (old) HNP #1 MN Proxy-CoA1 5 xxx Active Uplink, Downlink PBU(nMAG, Transient Binding) HNP MN-ID CoA ATT MN-LL-ID state Forwarding allowed 1 (old) HNP #1 MN Proxy-CoA1 5 xxx Transient Uplink, Downlink 2 (new) Proxy-CoA2 XXX Uplink PBU(nMAG), TIMEOUT_I, or PBU(pMAG, Lifetime=0) HNP MN-ID CoA ATT MN-LL-ID state Forwarding allowed 2 (new) HNP #1 MN Proxy-CoA2 5 XXX Active Uplink, Downlink IETF NetEXT WG IETFs New WG NetEXT (NETLMM Extension)
2009 7 (75th IETF - Stockholm, Sweden) PMIPv6 Extension Work Items on Consensus Localized routing bulk-registration Runtime LMA selection Not yet consensus and More discussion needed Multiple Interface support Inter-technology handovers New Research Items in PMIPv6
What Issues in NetEXT WG ? Scenario 1: Setting up Mobility Sessions on Demand Create additional mobility sessions on demand e.g., additional connection for a particular service A new mobility session with a new prefix is created LMA LMA Mobile IPTV flow Mobile IPTV flow PBU (HI=1) PBU (HI=1) ! MAG MAG MAG MAG VoIP flow VoIP flow WiMax 3G WiMax 3G HTTP flow WiBro 3G WiBro 3G MN MN New Research Items in PMIPv6
What Issues in NetEXT WG ? Scenario 2: Flow Mobility If another access is enabled on the MN, some of the existing flows could be moved over, to achieve, e.g., load balancing and better user experience LMA LMA Mobile IPTV flow Mobile IPTV flow PBU (HI=2) PBU (HI=1) ?Vertical ! MAG MAG MAG MAG VoIP flow VoIP flow WiMax 3G WiMax 3G WiBro 3G WiBro 3G MN MN New Research Items in PMIPv6
What Issues in NetEXT WG ? When the MN is connected to an existing MAG with if1 and then attaches to a new MAG with if2, it could either be 1) setting a new session on if2 or 2) performing a handover from if1 to if2 The new MAG needs to figure out if it is an initial attachment or a handover HOW? At handover, some sessions are left & the other sessions are moved. New Research Items in PMIPv6
Multi-interface Vertical Handover Handover optimization by using cross-layering techniques Cross-layering operation over IEEE /16 and 3GPP SAE/EPC IEEE Seamless Vertical Handover Complete Support for VariousVertical Handover Scenario Initial Attachment vs. Handover Per-flow mobility Horizontal Handover Vertical Handover Multiple Interface Management Multiple Flow Management A handover is initiated when mobile device exits the boundaries of an administrative domain. Single interface is used. A mobile device does need to move in order to initiate a handover. Multiple interfaces are required, but use one interface at a time. Simultaneous use of multiple interfaces and access networks. Association of an application with an interface Ability to split individual flows between links with respect to the requirements of the flows and the user preferences Complexity Level IETF Mif (Multi-interface) BoF - Interface selection - Address selection