Seamless Mobility over ICN Ravi Ravindran (ravi.ravindran@huawei.com) FG-IMT 2020, Demo Day Geneva, Dec, 2016
Outline • Mobility Objectives • Current Approach • 5G-ICN Architecture • AI/NI Name Space Split in ICN • ICN Mobility Control Plane • Handling Seamless Mobility • PoC Architecture and Demo
Current Objectives and Status Mobility Objectives: In-Session Mobility • Inter-RAT Mobility • Inter-Domain Mobility • Optimization Requirements • Minimize Packet Loss and Session disruption, – Optimal Routing – Minimal Control and User Plane overhead. – Mobility Today: Mobile IP is not deployed in a general infrastructure • – Complexity of a Control and User plane – LISP usage in data centers to handle VM mobility Cellular mobility is enabled through orthogonal standards such • as from 3GPP – 2G/3G/4G etc. Proposal for SDN based mobility in 5G • – Scalability and Efficiency challenges considering Centralized Control
Current Industry Thinking of Integration of Wifi and LTE Need for Identity, Mobility and Security complicates current Architecture. • Integration is based on introducing more gateway functions increasing Control and • User Plane Complexity. � � � � ICN offers them as part of its architecture.
Towards IMT2020/5G/ICN flat Architecture. LTE Network Architecture IMT2020/5G - ICN Architecture (Licensed/Unlicensed) Mobility/Security/Content- Centric Future Internet Arch. Service Controlle LTE Wifi IMT 2020/5G ICN Architecture [1] Current Architecture � Flat Application-centric Network • Hybrid 3GPP & IP Arch Architecture. � Cellular/Fixed Access Convergence • Disjoint Fixed and Cellular Access � No Gateways or Tunnels • Complex Control interfaces. � In-build Network Layer Mobility • Technology Specific (2G/3G/4G) � In-build Security, Storage and • IP Tunneling in Data Path • Gateways (…bottlenecks, sub optimal routing) Computing � Technology Neutral (any RAN/RAT) � Application-Centric Virtualization [1] Ravi Ravindran, Asit Chakraborti, Syed Obaid Amin, Aytac Azgin, G.Q.Wang, “ 5G-ICN : Delivering ICN Services over 5G using Network Slicing ”, http://arxiv.org/abs/1610.01182, Oct, 2016
AI/NI Name Space Split in ICN [1] • Application binds to Names • Names are associated with a Trust A/V AR/VR IoT Chain • Named Object and Security Model Applications Interest{/huawei/research/<person- • End point functions abstraction to phone>/<content-x>} Mobility Flow and Application Reliability Congestion Control Service • Flow and Congestion Control Transport Layer • Mobility can be enabled as a Service Interest{/huawei/research/<person- (publish name prefix for mobility) phone>/<content-x>:mobility-flag } • Binds Names to Network Identifiers Name Based Caching and Mobility • Name based routing (Flat, Routing Computing Hierarchical, Hybrid) Fragmentation ICN Security/Trust • In-Network Caching/Computing Interest{/huawei/research/<person-phone/content- • In-network Security x>:NI{/att/usa/santaclara/west} • Demonstrated its usefulness UDP/TCP/IP Ethernet/802.15.4 Wifi/LTE/5G/Optical infrastructure and Ad hoc scenarios. Any Transport • Variable length payload allows low bandwidth and very high bandwidth interfaces. In ICN Application binds to name (Application Identifiers) which can be resolved by the • application or by ICN to ( Network Identifiers ) We distinguish from ID/Locator terminology considering its usage in Host Centric Architectures, e.g. LISP. – There is not pre-binding in ICN, as NI only serves as routing guidance in case of cache miss – [1] Aytac Azgin, Ravi Ravindran, “Enabling Network Identifier in Information Centric Networks”, IETF/ICNRG, https://www.ietf.org/proceedings/97/slides/slides-97-icnrg-enabling-network-identifier-ni-in-information-centric-networks-to-support- optimized-forwarding-ravi-ravindran-00.pdf
Seamless Mobility in ICN/CCN By default CCN handles Consumer Mobility using caching and Interest re- • expression. Producer Mobility requires routing on names to resolve to current location. • – Scalability challenge and Poor Throughput [1] Current Approaches can be classified as Application Based approaches • – Anchor Based : Path Stretch and Naming Challenges [4] – Anchorless Based : New in-network signaling primitives [5] Signaling over head, Routing Challenges • Our solution Network Based - AI/NI split, proposed Forwarding Label in [2][3] • – Two features that help producer mobility are : Edge Resolution and Late Binding – Stable core routing based on NI – Limits Mobility Dynamics only to the network edge – It allows edge CCN nodes to resolve Interest in a service and topologically aware manner. – A name resolution infrastructure required to map the two name spaces. – Current scope is for a single administrative domain, inter-domain name resolution requires a global infrastructure that can meet Mobility requirements. [1] Aytac Azgin, Ravi Ravindran, G.Q.Wang “Mobility Study in Name Data Networking in Wireless Access Networks”, ICC, 2014. https://arxiv.org/pdf/1406.5521v1.pdf [2] Aytac Azgin, Ravi Ravindran, G.Q.Wang, “Seamless Mobility as a Service in Information Centric Networks”, 5G/ICN Workshop, ACM ICN Sigcomm, 2016, http://conferences2.sigcomm.org/acm-icn/2016/proceedings/p243-azgin.pdf [3] IETF/ICNRG, “Forwarding Label Support in CCN Protocol”, https://tools.ietf.org/html/draft-ravi-icnrg-ccn-forwarding-label-00 [4] H. Zhang, L. Zhang, “Kite: A Mobility Support Scheme for NDN”, Y. Zhang, ACM ICN 2014. [5] Jordan Auge et al, “Anchorless Producer Mobility in CCN”, ICN Sigcomm, 2015
Seamless Mobility using Forwarding Labels in ICN We augment the Interest packet with FL-Object [1]. • FL-Object contains the forwarding label, along with optional security binding • with name. The forwarders are enhanced to process the FL-Object. • Late binding allows Interest flows to be re-routed to UE’s current location. • [1] IETF/ICNRG, “Forwarding Label Support in CCN Protocol”, https://tools.ietf.org/html/draft- ravi-icnrg-ccn-forwarding-label-00
Seamless Mobility Through Late Binding Consumer Interest{} /PoA-3 FLT: Mobility Controller /producer -> /PoA-2 AI->NI FIB: Resolve{/producer} NI: PoA-1 /PoA-2 -> face-y /PoA-3 -> face-z /PoA-3 FLT: Content{/producer/content:Flag} /producer -> /PoA-2 FIB: FLT: /producer -> face-X /producer -> /PoA-3 FIB: Interest{/producer:FL /producer -> face-X =/PoA-3} NI:PoA-2 NI:PoA-3 (1)Register{/producer} (1)Register{/producer} De-register{/producer} Content{} Producer Handoff(PoA2-> PoA-3} In Network based mobility, network provides the PoA information allowing proactive late binding after • the de-registration from the UE If there is a candidate list of PoA, then the Interest can be multi-unicast to each one, until signaling from • the new PoA
ICN Seamless Mobility Demo System Control Plane ICN Control Plane DOCKER SWARM ONOS Swarm ICN Service Orchestrator Manager Controller ICN APPs Service Topology Orchestrating Nova REST API module Packet VBS Controller Device module Glance Conference Neutron Controller REST API Horizon Applicat Core (OpenFlow) ion Heat ICN Network OpenStack Controller Controller (OpenFlow) OVS Switch OVS Switch ICN Sync Proxy ICN Sync Proxy VM2 Forwarder VM2 Forwarder ICN ICN Hypervisor Sync Ctrlr Hypervisor Sync Ctrlr VM1 SAP SAP VM1 VM1 VBS Agent (Data Path) VBS Agent VSER1 VM3 VM3 IP Network APP SAL APP VSER1 SAL VSER1 ICN SAL: Service Access Layer VSER: Virtual Service Edge Router ICN VBS : Virtual Base Station SAP : Service Access Point
Mobility As a Service Features • Mobility control plane is virtualized, hence can be enabled on demand • Producers explicitly (de-)register request for their name space mobility Mobility Ser. ONOS VBS Controller OpenStack Map AI->NI /prefix->/vser-x (Nova/Glance/Heat) (5) Interest {/prefix} ICN Network Con. (1) Register_mobility{/prefix} (3) (5)Resole{/prefix/} (4) Mobility Con. (6)Response SAL flow policy (2) Pro. SAL VBS-A VBS-A ICN ICN VSER-2 VSER-1 ICN-R FLT FLT IP Network
Demo: A/V Conferencing with Mobility [3] Rx/Tx bit rates measured [1] A mobile Producer, at the producer end, with and 2 Consumers in A/V automated hand-over every Conferencing 20s between two APs. [2] Simulated Signal strength between the producer and the two APs [1] Asit Chakraborti et al, “Seamless Mobility as a Service in Information Centric Networks”, ICN Sigcomm, 2016
Performance Evaluation – Results • Application is a live video conferencing session • Handover events resulted in 1-to-2 block losses (~100ms), due to notification loss for the Consumer side Huawei Research 13 [1] Aytac Azgin et al, “Seamless Mobility as a Service in Information Centric Networks”, 5G/ICN Workshop, ICN Sigcomm, 2016
Conclusions • ICN allows flat mobile architecture and mobility over heterogeneous RATs, e.g. Wifi/LTE. • We enable mobility in ICN/CCN using the notion of AI/NI Split • Proposed architecture uses decentralized controllers to help with registration and resolution of name/locator mappings • Seamless mobility is achieved through proactive update of mobility states to help with re-routing Interests • Current work on realizing ICN service as multiple interacting virtual slices – Base Network, Mobility, Service slice (A/V, IoT etc.) Huawei Research 14
Recommend
More recommend
