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

• Hybrid 3GPP & IP Arch

• Disjoint Fixed and Cellular Access

• Complex Control interfaces.

• Technology Specific (2G/3G/4G)

• IP Tunneling in Data Path

• Gateways (…bottlenecks, sub optimal routing)

[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

Mobility/Security/Content-

Centric Future Internet Arch.

IMT2020/5G - ICN Architecture

�Flat Application-centric Network

Architecture.

� Cellular/Fixed Access Convergence

�No Gateways or Tunnels

�In-build Network Layer Mobility

�In-build Security, Storage and

Computing

�Technology Neutral (any RAN/RAT)

�Application-Centric Virtualization

Current Architecture

IMT 2020/5G ICN Architecture [1]

Service Controllers

(Licensed/Unlicensed)

LTE

Wifi

AI/NI Name Space Split in ICN [1]

• 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

ICN

A/V AR/VR IoT

Applications

Transport Layer

• Application binds to Names

• Names are associated with a Trust

Chain

• Named Object and Security Model

ReliabilityFlow and

Congestion Control

• End point functions abstraction to

Application

• Flow and Congestion Control

• Mobility can be enabled as a Service

(publish name prefix for mobility)

Name Based

Routing

Caching and

Computing

Mobility

Security/Trust

Any Transport

UDP/TCP/IP Ethernet/802.15.4 Wifi/LTE/5G/Optical

•Binds Names to Network Identifiers

• Name based routing (Flat,

Hierarchical, Hybrid)

• In-Network Caching/Computing

• In-network Security

•Demonstrated its usefulness

infrastructure and Ad hoc scenarios.

• Variable length payload allows low

bandwidth and very high bandwidth

interfaces.

Fragmentation

Interest{/huawei/research/<person-

phone>/<content-x>}

Interest{/huawei/research/<person-

phone>/<content-x>:mobility-flag }

Interest{/huawei/research/<person-phone/content-

x>:NI{/att/usa/santaclara/west}

[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

Mobility

Service

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

• 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

NI: PoA-1

NI:PoA-2 NI:PoA-3

(1)Register{/producer}

FLT:

/producer -> /PoA-2

FIB:

/producer -> face-X

Producer

Consumer

Mobility Controller

AI->NI

FLT:

/producer -> /PoA-2

FIB:

/PoA-2 -> face-y

/PoA-3 -> face-z

Interest{}

Content{}

Handoff(PoA2-> PoA-3}

/PoA-3

De-register{/producer}

Interest{/producer:FL

=/PoA-3}

(1)Register{/producer}

FLT:

/producer -> /PoA-3

FIB:

/producer -> face-X

Content{/producer/content:Flag}

Resolve{/producer}

/PoA-3

DOCKER

SWARM

ICN Seamless Mobility Demo System Control Plane

RE

ST

AP

I

REST API

Service

Orchestrating

module

Topology

moduleDevice Packet

Applicat

ion Core

ICN Service Orchestrator ONOS

Controller

ICN

Hypervisor

SAP

OVS Switch

VSER1

VM1

VBS Agent

VM3

Glance

Nova

OpenStack

Controller

Neutron

Horizon

Heat

ICN

Forwarder

ICN

Hypervisor

SAP

OVS Switch

Sync Proxy

Sync Ctrlr

VSER1

VM1

VM2

VBS Agent

VM3

(OpenFlow)

IP NetworkVSER1

ICN

Forwarder

ICN Network

Controller

ICN APPs

VBS Controller

Swarm

Manager

(OpenFlow)

Conference

Controller

ICN

SAL

(Data Path)

Sync Proxy

VM2

Sync Ctrlr

VM1

ICN Control Plane

VSER: Virtual Service Edge Router

VBS : Virtual Base Station

APP

ICN

SALAPP

SAL: Service Access Layer

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

ICN

Pro. SAL

IP Network

ICN

Con.

FLT FLT

VBS Controller ONOSOpenStack

Mobility Ser.

VSER-1 VSER-2ICN-R

VBS-A VBS-A

(Nova/Glance/Heat)

ICN Network Con.

SAL

Map AI->NI

/prefix->/vser-x

(1) Register_mobility{/prefix}

(2)

(4) Mobility

flow policy

(5)Resole{/prefix/}

(6)Response

(5) Interest {/prefix}

(3)

Demo: A/V Conferencing with Mobility

[1] A mobile Producer,

and 2 Consumers in A/V

Conferencing

[2] Simulated Signal strength between the producer and the two APs

[3] Rx/Tx bit rates measured

at the producer end, with

automated hand-over every

20s between two APs.

[1] Asit Chakraborti et al, “Seamless Mobility as a Service in Information Centric Networks”, ICN Sigcomm, 2016

Performance Evaluation – Results

Huawei Research 13

• 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

[1] Aytac Azgin et al, “Seamless Mobility as a Service in Information Centric Networks”, 5G/ICN Workshop, ICN Sigcomm, 2016

Conclusions

Huawei Research 14

• 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.)