네트워크 기반의 Flow Mobility 기술 Youn-Hee Han Korea University of Technology and Education Laboratory of Intelligent Networks 2009.12 제.

Presentation on theme: "네트워크 기반의 Flow Mobility 기술 Youn-Hee Han Korea University of Technology and Education Laboratory of Intelligent Networks 2009.12 제."— Presentation transcript:

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

2 2/32 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/32 제 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! 4/32 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

5 Why Network-based? Operators are even now deploying their non- standardized network-based IP mobility solution 5/32 No changes to the client devices or the underlying infrastructure are required No Stable MIPv4/v6 stack executed in Microsoft Windows OS [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 [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 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

6 Proxy Mobile IPv6 (PMIPv6) Proxy Mobile IPv6 [IETF RFC 5213, August 2008] LMM (Localized Mobility Management) Domain MAG LMA Proxy Binding Update/Ack. (PBU/PBA) Control messages exchanged by MAG to LMA to establish a binding between MN-HoA and Proxy-CoA Home Network Proxy Care of Address (Proxy-CoA) The address of MAG That will be the tunnel end-point IP Tunnel IP-in-IP tunnel between LMA and MAG MAG LMA: Localized Mobility Agent MAG: Mobile Access Gateway LMA Address (LMAA) MN’ Home Address (MN-HoA) MN continues to use it as long as it roams within a same domain That will be the tunnel entry-point MN’s Home Network (Topological Anchor Point) MN’s Home Network Prefix (MN-HNP) CAFE:2:/64 movement 6/32 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

7 RA*: MN 의 Prefix 를 Policy Store 에서 수신한 경우의 Router Advertisement RA**: MN 의 Prefix 를 LMA 에서 수신한 경우의 Router Advertisement MNMAGAAA&Policy StoreLMACN 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** [MN-HoA:CN](data) [Proxy-CoA:LMAA][MN-HoA:CN](data) [MN-HoA:CN](data) Tunnel Setup PBU: Proxy Binding Update PBA: Proxy Binding Ack. DHCP Server DHCP Request DHCP Response DHCP Request DHCP Response Optional 7/32 PMIPv6 Operation Flow 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

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

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

10 PMIPv4 over WiMAX In Split PMA (Proxy Mobility Agent  MAG & FA) Model 10/32 “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 UE S-GW/(MAG) GTP-U Tunnel P-GW/LMA IP-in-IP Tunnel eNodeB P-GW: access gateway towards Packet Data Networks (similar to the GGSN) - PMIPv6 will be mainly used for inter-system handovers (i.e. handovers between 3GPP and non-3GPP accesses) Ref.] I. Guardini et al., “Mobile IPv6 deployment opportunities in next generation 3GPP networks,” 16 th IST Mobile&Wireless Communication Summit, Budapest, Hungary 1-5, July 2007 Optional! 11/32 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

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

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

14 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 가 고려하는 시나리오 Dual Stack Support in PMIPv6 Cellular IP network WLAN IP Network WiBro IP Network RAS LTE BS WLAN AP IPv4 IPv6 Private IPv4 NAT AAA DS-PMIPv6 LMA IPv4 IPv6 IPv4 Application (VoD, IP-Phone…) IPv6 Application (VoD, IP-Phone…) MN 14/32 DS-PMIPv6 MAG 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

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

16 6-in- udp-in-4 Tunnel or GTP 4-in- udp-in-4 Tunnel or GTP 6-in-4 Tunnel or GTP 4-in-4 Tunnel or GTP MAG 와 LMA 사이의 시그널링 및 터널 설정 LMA ( 바인딩 관리 : IPv6 HoA & IPv4 HoA  IPv4 or IPv6 Proxy-CoA ) MAG IPv4- UDP- IPv6- PBU IPv4- UDP- IPv6- PBAck 6-in-6 Tunnel or GTP 4-in-6 Tunnel or GTP MAG IPv6- PBU IPv6- PBAck NAT MN 이 IPv6 네트워크로 이동할 때 MN 이 IPv4 네트워크로 이동할 때 MN 이 Private IPv4 네트워크로 이동할 때 IPv4- UDP- IPv6- PBU IPv4- UDP- IPv6- PBAck DS(Dual Stack)-PMIPv6 16/32 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

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

18 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 1Subnet 2 MAG3 (PC3) Subnet 3 Notebook1Notebook2Notebook1 802.11g802.11a 192.168.1.2 192.168.3.2 192.168.1.1 192.168.3.1 192.168.4.1192.168.4.2 10.0.1.110.0.2.1 10.0.1.210.0.2.2 10.0.1.1 10.0.1.2 10.0.101.110.0.102.1 10.0.101.1 192.168.5.1 192.168.5.2 192.168.5.1 DS-PMIPv6 테스트베드 -2 18/32 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

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

20 75&76 th IETF’s NetExt WG & NetEXT2 BoF 75 th 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 75 th IETF’s New BoF – NetExt2 (NETLMM Extension 2) 2009 년 7 월 첫 BoF 회의 More controversial issues  Multiple Interface support  Flow Mobility  Inter-technology handovers 76 th IETF’s NetExt WG 2009 년 11 월 Above all items becomes work items of NetExt WG 20/32 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

21 IETF’s Mobility Management Protocols 이동성 관리 연구주제와 IETF 표준화 진행 상황 21/32 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵 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 Host-based CMIPv6 Network-based Proxy MIPv6 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] 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].

22 Motivation & Goal “Multiple CoA Reg [RFC 5648]”extends HA and CN to allow the binding of more than one CoA to the HoA. Flow Mobility in CMIPv6 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 회 차세대 이동통신망을 위한 이동성관리 워크샵 22/32

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

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

25 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵 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 Flow Mobility Scenario in CMIPv6 Router HA Router HA Router MN 3G 새로운 인터페이스로 세션을 이동  Vertical 핸드오버 VoIP 세션만 옮겨아지 ! MN 3GWiBro VoIP flow Mobile IPTV flow WiBro3GWiBro3G WiBro Mobile IPTV flow VoIP flow Binding Update with Binding ID & Flow ID 25/32

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

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

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 WiMax MAG LMA PBU MAG 3G 단말 3GWiBro MAG LMA PBU MAG 단말 3GWiBro WiMax3G 다른 인터페이스의 스위치 를 올려서 단순하게 접속만 시도했군 ! 플로우 이동은 없고 … 이것을 어떻게 알지 ? Mobile IPTV flow VoIP flow Mobile IPTV flow VoIP flow HTTP flow 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵 28/32

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 29/32 MAG LMA PBU MAG LMA MAG 단말 3G 새로운 인터페이스로 한 개의 세션을 이동하고 있네 … 이것을 어떻게 알지 ? 단말 3GWiBro VoIP flow Mobile IPTV flow WiMax3GWiMax3G WiBro Mobile IPTV flow VoIP flow PBU 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

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

31 Flow Mobility in PMIPv6 Ways to achieves (introduced by Jari Arkko. Nov. 2009 IETF 76 th ) 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 31/32 제 3 회 차세대 이동통신망을 위한 이동성관리 워크샵

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