+ All Categories
Home > Documents > Distributed Mobility Management

Distributed Mobility Management

Date post: 18-Dec-2015
Category:
Upload: fneklwemf
View: 13 times
Download: 0 times
Share this document with a friend
Description:
Distributed Mobility Management for future 5G networks
Popular Tags:
29
http://www.ict-ijoin.eu/ @ict_ijoin EU FP7 Project iJOIN Distributed Mobility Management for future 5G networks iJOIN Winter School Feb. 23 rd 2015 Carlos J. Bernardos (Universidad Carlos III de Madrid) Contact: [email protected] iJOIN: Interworking and JOINt Design of an Open Access and Backhaul Network Architecture for Small Cells based on Cloud Networks
Transcript
  • http://www.ict-ijoin.eu/ @ict_ijoin

    EU FP7 Project iJOIN

    Distributed Mobility Management for future 5G networks

    iJOIN Winter School

    Feb. 23rd 2015 Carlos J. Bernardos (Universidad Carlos III de Madrid)

    Contact: [email protected]

    iJOIN: Interworking and JOINt Design of an Open Access and Backhaul Network Architecture for Small Cells based on Cloud Networks

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 2 ))

    Outline

    Motivation Mobility management in 5G networks Why Distributed Mobility Management?

    Distributed Mobility Management: main solutions

    PMIPv6-based Routing-based SDN-based

    Evaluation of the DMM solutions

    Setup Experimental results

    Conclusions

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 3 ))

    Motivation: Mobility management in 5G networks

    5G networks should cope with mobile traffic increase 3 major trends to meet the traffic demand:

    Enhancement of the wireless access Migration towards smarter (& cheaper) network management Flatter networks

    Mobility is a key aspect for mobile/cellular networks

    5G networks will serve more heterogeneous users & services Smaller cells Reduced OPEX & CAPEX

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 4 ))

    Motivation: Mobility management in 5G networks

    Operators and vendors are continuously searching strategies to evolve mobile networking

    Distributed Mobility Management (DMM) Flat architecture paradigm

    Flexible and dynamic traffic anchoring

    Enhanced radio interfaces for higher

    data rates More efficient

    network architecture

    Smarter access network enriched with new features

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 5 ))

    Motivation: Why Distributed Mobility Management?

    The classical mobility protocols are centralised MIPv4, MIPv6, PMIPv6, GTP Central entity (mobility anchor) anchors all the traffic

    All traffic traverses the mobility anchor

    A mobility anchor is usually deployed in the core Some (very) limited differentiation per service

    Even if directed to peers nearby Even if the traffic is not critical for the operators

    Black or white approach

    Mobility support is provided or not It is not possible to provide fine-grained flow mobility

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 6 ))

    Motivation: Why Distributed Mobility Management?

    DMM: Paradigm to design a novel flat architecture Flexible data plane

    Local breakout to IP networks at access routers (similar to SIPTO) Distributed mobility functions

    from the core to the edge of the mobile network

    Centralized and hierarchical architecture

    (current deployments)

    Distributed and flat architecture

    (future deployments?)

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 7 ))

    Distributed Mobility Management: main solutions

    Distributed Mobility Management is a way of designing a flat mobility architecture

    The IETF DMM WG is the main discussion venue

    Three main DMM approaches: Mobile IP based

    Routing based

    SDN based

    We next analyse each of them

    legacy solution

    5G solution

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 8 ))

    DMM main solutions

    A mobility-enabled access router is called DMM-GW

    Each DMM-GW owns a unique IPv6 prefix pool Assigns one to each

    MN on link Plain router for prefix

    when MN on-link Tunneling used to

    route prefix when MN moves

    DMM-GW DMM-GWs

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 9 ))

    DMM main solutions: PMIPv6-based

    This solution is based on Proxy Mobile IPv6 Belongs to IP mobility solutions Adapts PMIPv6 to a flat network

    Partially distributed

    Control Mobility Database (CMD) is the central entity

    responsible of managing the mobility

    Networks nodes involved: DMM-GWs

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 10 ))

    DMM main solutions: PMIPv6-based

    1st attachment operations

    RS

    PBU PBA RA

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 11 ))

    DMM main solutions: PMIPv6-based

    Traffic exchange with CN1

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 12 ))

    DMM main solutions: PMIPv6-based

    Handover operations

    RS

    PBU PBA RA PBU PBA

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 13 ))

    DMM main solutions: PMIPv6-based

    IP-in-IP tunnel for traffic redirection

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 14 ))

    DMM main solutions: Routing-based

    Removes any anchors, let the routing mechanism re-establish the path

    Fully distributed

    This solution employs BGP as routing protocol

    Networks nodes involved: DMM-GWs All the BGP routers in the network domain

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 15 ))

    DMM main solutions: Routing-based

    1st attachment operations

    AUTH

    DNS RA BGP-Up

    BGP-Up

    BGP-Up

    BGP-Up

    BGP-Up

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 16 ))

    DMM main solutions: Routing-based

    Traffic exchange with CN1

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 17 ))

    DMM main solutions: Routing-based

    Handover operations

    AUTH

    DNS RA BGP-Up

    BGP-Up

    BGP-Up

    BGP-Up

    BGP-Up

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 18 ))

    DMM main solutions: Routing-based

    Traffic redirection

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 19 ))

    DMM main solutions: SDN-based

    SDN based mobility solution with service differentiation support k Egress Routers (ER) are assigned to each MN

    Egress Routers used for service differentiation

    Partially distributed

    Network Controller (NC) is the central entity responsible of managing the mobility

    Networks nodes involved: DMM-GWs, Egress Routers

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 20 ))

    DMM main solutions: SDN-based

    1st attachment operations, k=3

    RS

    OF OF OF OF RA

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 21 ))

    DMM main solutions: SDN-based

    Traffic exchange with CN1 and CN2

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 22 ))

    DMM main solutions: SDN-based

    Handover operations

    RS

    OF OF OF OF OF RA

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 23 ))

    DMM main solutions: SDN-based

    Traffic redirection

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 24 ))

    DMM experimental evaluation: setup

    802.11 access 3 DMM-GW 1 CMD/NC/DNS 1 MN & 1 CN

    PMIPv6 Routing SDN

    Linux-based platform Some code release as

    Open Source: http://odmm.net/

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 25 ))

    DMM experimental evaluation: Handover latency

    Layer-2 handover Interval between Deauthentication and Association response 802.11

    messages

    Layer-3 configuration Interval between Deauthentication and Router Advertisement messages

    IP flow recovery

    Interval between the last IP packet received by the MN before the handover and the first IP packet received after the handover

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 26 ))

    DMM experimental evaluation: Handover latency

    Quagga daemon takes on average ~3s since a new route is installed until the

    daemon starts to distribute the BGP

    updates back-to-back

    Router protocols are not designed to react

    immediately, ping-pong effects and messages

    flooding

    IP flow recovery

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 27 ))

    DMM experimental evaluation: Handover latency

    Layer-3 conf. composition Layer 2 + Router Adv. reception

    MN gap: time needed by the MN to receive the Association response and send the Router

    solicitation

    Tx time: time needed for packets transmission

    MN gap (2): In Routing solution, the MN does not send any Router

    solicitation

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 28 ))

    Conclusions

    Objectives of this work Evaluation and comparison of the main DMM solutions families

    Contribution

    SDN-based solution has been designed from scratch

    All the solutions have been prototyped Feasibilitys proof of each solution

    Experimental evaluation

    PMIPv6 and SDN can provide mobility in a timely manner At current state Routing-based is not a viable solution

    [1] Distributed Mobility Management for future 5G networks: overview and analysis of existing approaches, F. Giust, L. Cominardi and CJ. Bernardos, IEEE Communications Magazine, Volume 53, Issue 1, pp. 142-149, Jan. 2015

  • http://www.ict-ijoin.eu/ @ict_ijoin (( 29 ))

    Thank you for your attention!

    EU FP7 Project iJOINDistributed Mobility Managementfor future 5G networksOutlineMotivation: Mobility management in 5G networks Motivation: Mobility management in 5G networksMotivation: Why Distributed Mobility Management?Motivation: Why Distributed Mobility Management?Distributed Mobility Management: main solutionsDMM main solutionsDMM main solutions: PMIPv6-basedDMM main solutions: PMIPv6-basedDMM main solutions: PMIPv6-basedDMM main solutions: PMIPv6-basedDMM main solutions: PMIPv6-basedDMM main solutions: Routing-basedDMM main solutions: Routing-basedDMM main solutions: Routing-basedDMM main solutions: Routing-basedDMM main solutions: Routing-basedDMM main solutions: SDN-basedDMM main solutions: SDN-basedDMM main solutions: SDN-basedDMM main solutions: SDN-basedDMM main solutions: SDN-basedDMM experimental evaluation: setupDMM experimental evaluation: Handover latencyDMM experimental evaluation: Handover latencyDMM experimental evaluation: Handover latencyConclusionsFoliennummer 29


Recommended