1 / 32

네트워크 기반의 Flow Mobility 기술

네트워크 기반의 Flow Mobility 기술. Youn-Hee Han Korea University of Technology and Education Laboratory of Intelligent Networks http://link.kut.ac.kr 2009.12. Network-based IP Mobility Support. Recent Trend of IP Mobility. Network-based! No change to host

moanna
Download Presentation

네트워크 기반의 Flow Mobility 기술

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. 네트워크 기반의 Flow Mobility 기술 Youn-Hee Han Korea University of Technology and EducationLaboratory of Intelligent Networks http://link.kut.ac.kr 2009.12 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  2. Network-based IP Mobility Support 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  3. Recent Trend of IP Mobility • Network-based! • No change to host • Mobility handled by the network, and transparent to the host • IETF’s much activities • Working Groups • NetLMM (Proxy Mobile IP), NetExt, Mext, Mipshop, Mif, Mip4 • BoF • NetExt2 • 3GPP/PP2 and WiMAX operators are now showing their STRONG interests and activities for network-based IP mobility solution 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  4. Why Network-based? • Host-based IP Mobility (CMIPv4/v6) has not been widely deployed due to several factors • Implementation issues • IPsec and IKEv1 • Deployment issues • No cohesive mobility architecture • Negligible deployment of IPv6 • Operational issues • Layer 3 signalling via radio link • Layer 8 issues (Financial/Human/Political/FUD/…) • Many operators elected to create their own protocols (eg. GTP), or • They picked other IETF mobility protocols (Proxy MIP etc.) • Money! 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  5. Why Network-based? • Operators are even now deploying their non-standardized network-based IP mobility solution • [CMIPv6’s Problems] • 1) Too heavy specification to be implemented at a small terminal • - RFC 3344 (MIPv4): 99 pages • - RFC 3775 (MIPv6): 165 pages • 2) Battery problem • 3) Waste of air resource No Stable MIPv4/v6 stack executed in Microsoft Windows OS No changes to the client devices or the underlying infrastructure are required 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  6. Proxy Mobile IPv6 (PMIPv6) • Proxy Mobile IPv6 [IETF RFC 5213, August 2008] LMA: Localized Mobility AgentMAG: Mobile Access Gateway IP Tunnel IP-in-IP tunnel between LMA and MAG LMA Home Network MN’s 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 MN’s Home Network Prefix (MN-HNP) CAFE:2:/64 MN’ Home Address (MN-HoA) MN continues to use it as long as it roams within a same domain Proxy Care of Address (Proxy-CoA) The address of MAG That will be the tunnel end-point 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  7. PMIPv6 Operation Flow PBU: Proxy Binding UpdatePBA: 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) 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  8. PMIPv6 Features • Home in Any Place • MAG sends the RA (Router Advertisement) messages advertising MN’s 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 MN’s 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. 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  9. DNS HA or LMA NMS IP Network Internet AAA/Policy Store E R E R ACR/MAG L2 Switch BS/RAS PSS ACR ACR PMIPv6 over WiBro/WiMAX • Proxy Mobile IPv6 over WiBro/WiMAX TTA 단체표준, “와이브로에서의 프록시 모바일 IPv6 적용,”TTAK.KO-10.0284, Dec. 2008 "WiMAX Forum Network Architecture (Stage 3: Detailed Protocols and Procedures) Release 1 Version 1.2.3" PreviousMAG PreviousMAG 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  10. PMIPv4 over WiMAX • In Split PMA (Proxy Mobility Agent  MAG & FA) Model “WiMAX Forum/3GPP2 Proxy Mobile IPv4,” IETF Internet Draft - draft-leung-mip4-proxy-mode-10.txt 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  11. 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) 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  12. PMIPv6 in 3GPP LTE/EPC • Proxy Mobile IPv6 over LTE • Vertical handover scenario LMA LMA 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  13. Performance Test: CMIPv6 vs. PMIPv6 • Test Results with Heavy Traffic (presented at MobiWorld 2008 conference) • Encoding Rate: 2Mbps UDP Throughput of MIPv6 UDP Throughput of PMIPv6 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  14. WiBro IP Network Cellular IP network Dual Stack Support in PMIPv6 • Dual-Stack Support in Proxy MIPv6 • draft-ietf-netlmm-pmip6-ipv4-support-17.txt (Sep. 2009) • PMIPv6 기반 IPv4 Transport 및 IPv4 Home Address Mobility 지원 • DS-PMIPv6가 고려하는 시나리오 IPv4 Application(VoD, IP-Phone…) RAS DS-PMIPv6LMA MN IPv4 DS-PMIPv6MAG IPv4 LTE BS IPv6 WLANIP Network IPv6 NAT Private IPv4 AAA WLAN AP IPv6 Application(VoD, IP-Phone…) 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  15. DS(Dual Stack)-PMIPv6 • PMIPv6’s Dual-Stack Support [Mobility Binding] HoAv4 and HoAv6 PBU (HoAv6, Proxy CoAv6, HoAv4) Proxy CoAv6 Dual Stack MNor IPv4 MN IPv4 traffic CNv4  HoAv4 IPv6 Tunnel (LMAAv6Proxy CoAv6) IPv6 traffic CNv6->HoAv6 Dual Stack MAG Only-IPv6 enabled (Proxy CoAv6) Dual Stack LMA Only-IPv6 enabled (LMMAv6) <MN in IPv6 domain> [Mobility Binding] HoAv4 and HoAv6 PBU (HoAv6, Proxy CoAv4, HoAv4) Dual Stack MNor IPv4 MN Proxy CoAv4 IPv4 traffic CNv4  HoAv4 IPv4 Tunnel (LMAAv4Proxy CoAv4) IPv6 traffic CNv6->HoAv6 Dual Stack MAG Only-IPv4 enabled (Proxy CoAv4) Dual Stack LMA Only-IPv4 enabled (LMAAv4) <MN in IPv4 domain> 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  16. 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-6Tunnel orGTP 4-in-6Tunnel or GTP 6-in-4Tunnel or GTP 4-in-4Tunnel or GTP 6-in-udp-in-4Tunnel or GTP 4-in-udp-in-4Tunnel or GTP MAG MAG MAG MN 이 IPv6 네트워크로 이동할 때 MN 이 IPv4 네트워크로 이동할 때 MN 이 PrivateIPv4 네트워크로 이동할 때 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  17. DS-PMIPv6 테스트베드-1 v4/v6 VoD Server CN eth1) 192.168.2.1 3ffe:2::1/64 ETRI (2007, 2008) LMA V4/V6 network MN has Dual Stack and both addresses are always enabled eth0) 192.168.2.2 3ffe:2::2/64 LMA가 MN에게 할당할 Prefix Pool 3ffe:1:3:1::/64 ~ 3ffe:1:3:ffff::/64 eth0) 192.168.1.1 3ffe:1::1/64 NAT 192.168.1.3 Private V4 network V6 network eth0) 10.0.0.1 MAG3 V4 network eth0) 3ffe:1::2/64 MAG1 eth0) 192.168.1.2 MAG2 ra0) 10.0.1.1 3ffe:1:3::1/64 fe80::1 ra0) 192.168.101.1 3ffe:1:1::1/64 fe80::1 ra0) 192.168.102.1 3ffe:1:2::1/64 fe80::1 SSID: PMIP3 SSID: PMIP1 SSID: PMIP2 초기 실행: v4 VoD Client 초기 실행: v6 VoD Client 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  18. Subnet 4 VoD (PC4) 192.168.4.1 192.168.4.2 LMA (PC0) 192.168.3.1 192.168.1.1 192.168.3.2 192.168.1.2 802.11g 802.11a NAT2 NAT1 10.0.1.1 10.0.2.1 10.0.1.1 10.0.1.2 10.0.2.2 10.0.1.2 Subnet 1 Subnet 2 Subnet 3 MAG1 (PC1) MAG2 (PC2) MAG3 (PC3) 10.0.101.1 10.0.102.1 10.0.101.1 192.168.5.1 192.168.5.2 192.168.5.1 192.168.5.1 Notebook1 Notebook1 Notebook2 Notebook1 DS-PMIPv6 테스트베드-2 KT (2007): DS-PMIPv6 with Only Private IPv4 Network and IPv4 Application 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  19. Multiple Interface, Flow Mobility, and Vertical Handover in Proxy MIP 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  20. 75&76th IETF’s NetExt WG & NetEXT2 BoF • 75th IETF’s New WG – NetExt (NETLMM Extension) • 2009년 7월 첫 WG 회의 (75th IETF - Stockholm, Sweden) • PMIPv6의 Extension 기술에 대한 표준화 • Work Items on Consensus • Localized routing, bulk-registration, Runtime LMA selection • 75th IETF’s New BoF – NetExt2 (NETLMM Extension 2) • 2009년 7월 첫 BoF 회의 • More controversial issues • Multiple Interface support • Flow Mobility • Inter-technology handovers • 76th IETF’s NetExt WG • 2009년 11월 • Above all items becomes work items of NetExt WG 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  21. IETF’s Mobility Management Protocols • 이동성 관리 연구주제와 IETF 표준화 진행상황 Host-based CMIPv6 Network-basedProxy MIPv6 Proxy Mobile IPv6 [RFC 5213, Aug. 2008] IPv4 Support for Proxy Mobile IPv6 [draft-ietf-netlmm-pmip6-ipv4-support-17] Fast Handovers for Proxy Mobile IPv6 [draft-ietf-mipshop-pfmipv6-11] Multiple Care-of Addresses Registration & Flow Bindings in Proxy Mobile IPv6 [draft-krishnan-netext-intertech-ps-02] [draft-hui-netext-multihoming-00] [draft-melia-netext-muho-solution-00] [draft-xia-netext-flow-binding-00] [draft-hui-netext-service-flow-identifier-01] [draft-koodli-netext-flow-handover-00] . . . Mobility Support in IPv6 [RFC 3775, June 2004] Mobile IPv6 Support for Dual Stack Hosts and Routers [RFC 5555, June 2009] Fast Handovers for Mobile IPv6 [RFC 4068, July 2005] Multiple Care-of Addresses Registration [RFC 5648, Oct. 2009] Flow Bindings in Mobile IPv6 and NEMO Basic Support [draft-ietf-mext-flow-binding-04] Horizontal Handover A handover is initiated when mobile device exits the boundaries of an administrative domain. Single interface is used. Vertical Handover A mobile device does need to move in order to initiate a handover. Multiple interfaces are required, but use one interface at a time. Complexity Level Multiple Interface Management Simultaneous use of multiple interfaces and access networks. Association of an application with an interface Multiple Flow Management Ability to split individual flows between links with respect to the requirements of the flows and the user preferences 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  22. Flow Mobility in CMIPv6 • Motivation & Goal • “Multiple CoA Reg [RFC 5648]”extends HA and CN to allow the binding of more than one CoA to the HoA. A new Binding Identification (BID) number is created for each binding and sent in the Binding Update. For the data packets, the binding cache lookup may involve policy or flow filters to retrieve a correspondent BID per packet. However, the binding cache lookup using policy or flow filters is out of scope for this document. 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  23. Flow Mobility in CMIPv6 • Motivation & Goal • “Flow Binding” allows a mobile node/mobile router to bind a particular flow to a particular CoA with HA and CN. #2 #1 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  24. Flow Binding Operation • Binding & Flow Information Management in HA and CN FID1, IPs, Ports, … FID2, IPs, Ports, … FID3, IPs, Ports, … FID1, IPs, Ports, … FID2, IPs, Ports, … FID3, IPs, Ports, … 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  25. Flow Mobility Scenario in CMIPv6 • Supported Scenario • Scenario 1: Move some of flows to a new interface • 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 Binding Update with Binding ID & Flow ID HA HA Mobile IPTVflow Mobile IPTVflow Router Router Router Router VoIPflow VoIPflow WiBro 3G WiBro 3G 새로운 인터페이스로 세션을 이동  Vertical 핸드오버 VoIP 세션만 옮겨아지! WiBro 3G WiBro 3G MN MN 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  26. Flow Mobility Scenario in CMIPv6 • Supported Scenario • Scenario 2: 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 Binding Update with Binding ID (No Flow ID) LMA LMA Mobile IPTVflow Mobile IPTVflow HTTPflow Router Router Router Router Binding Update with Binding ID Flow ID & Traffic Selector VoIPflow VoIPflow WiBro 3G WiBro 3G 다른 인터페이스의 스위치를 올려서 단순하게 접속만 시도 세션이동은 하지 말아야지… HTTP 세션은 3G 인터페이스로 열어야지… WiBro 3G WiBro 3G MN MN IP Mobility 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  27. Binding Update Extension in CMIPv6 • Extension of Binding Update Message & Traffic Selector Binding Update IPv6 Binding Update Header BindingUpdate Binding ID Mobility Option Flow ID Mobility Option Traffic Selector Sub-option 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  28. Flow Mobility in PMIPv6 • Flow Mobility 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 IPTVflow Mobile IPTVflow PBU 다른 인터페이스의 스위치를 올려서 단순하게 접속만 시도했군 !플로우 이동은 없고… 이것을어떻게 알지? PBU MAG MAG MAG MAG VoIPflow VoIPflow WiMax 3G WiMax 3G HTTPflow WiBro 3G WiBro 3G 단말 단말 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  29. Flow Mobility in PMIPv6 • Flow Mobility 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 IPTVflow 새로운 인터페이스로 한 개의 세션을 이동하고 있네… 이것을 어떻게 알지? Mobile IPTVflow PBU PBU MAG MAG MAG MAG VoIPflow VoIPflow WiMax 3G WiMax 3G WiBro 3G WiBro 3G 단말 단말 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  30. Flow Mobility in PMIPv6 • A proposal to achieve flow mobility In PMIPv6 • draft-hui-netext-service-flow-identifier-01 (fromChina Mobile) • 특징 • MAG가 LMA에게 특정 서비스 플로우정보를 알려주기 위한 Service Flow Identifier (SF-ID) Option 포멧을정의하고 이것을 PBU 및PBA에 포함 • SF-ID가 포함된 PBU를 올려 보내는 시점 • MAG가 단말의 임의의 인터페이스로부터 새로운 서비스 플로우에 속한 데이터를 받고 그 트래픽을 분석한 이후 • 문제점 • 단말로부터 새로운 서비스 플로우의 데이터 트래픽, 즉Uplink 트래픽이MAG로 보내어질 때만 그러한 서비스 플로우 바인딩이 요청될 뿐임 • 다른 상대 단말로부터 해당 단말로 트래픽이먼저 보내어질 때, 즉 Downlink 트래픽이MAG로 보내어질 때에는 서비스 플로우 바인딩이 요청될 수 없다. 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  31. Flow Mobility in PMIPv6 • Ways to achieves (introduced by Jari Arkko. Nov. 2009 IETF 76th) • 1. Using Link-layer mechanisms • Jari Arkko (Area Director)’s preference • 2. Using Host mobility protocols • MIP/HIP/... used on the host for changing from one interface to another, even if the network does proxy mobility within one interface • MIP guys’ preference • 3. PMIP extensions to signal interface movements • RS/RA extensions to request moving the prefix from the old interface to the new interface • PMIP guys’ preference 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

  32. Summary • Summary • Network-based IP Mobility Management • Proxy Mobile IPv6 (RFC 5213) • PMIPv6 in WiMAX/WiBro/3GPP • Dual Stack Support • draft-ietf-netlmm-pmip6-ipv4-support-17 • IPv4/v6 Transport Network Support • IPv4/v6 Home Address Mobility • Complete Support for Various Vertical & Flow Handover Scenarios • “Initial Attachment” vs. “Handover” • Per-flow mobility • Inherent difficulty to achieve in PMIPv6 • Many proposals in IETF NetExt WG 제3회 차세대 이동통신망을 위한 이동성관리 워크샵

More Related