Review on Recent Mobility Management Short History for …link.koreatech.ac.kr/talks_old/2012/Review_Recent_MM.pdf · 2015-06-21 · Review on Recent Mobility Management Technology-LTE/SAE

Review on Recent Mobility Management

Technology- LTE/SAE Mobility and DMM/DHT -

2012. 8

Youn-Hee [email protected]

http://link.koreatech.ac.kr

Contents Overview on Recent Mobility Management Research

– Why Mobility Management– Short History for Mobility Service and Protocols– Approaches for Mobility Management Research

LTE/SAE Mobility Management– LTE/SAE Architecture & Entities– PDN Connectivity Service– Mobility Management

• Location management & Handover management

Distributed and Dynamic Mobility Management– Concepts of Distributed Mobility Management– Dynamic Mobility Management– Distributed Hash Table

LINK@KoreaTech 2

Overview on Recent Mobility Management Research

LINK@KoreaTech 3

Why Mobility Management Research?

LINK@KoreaTech 4

Source: ITU-T

Source: Morgan Stanley Research

Why Mobility Management Research?

LINK@KoreaTech 5


[Business-oriented Motivation (from 4WARD Project)]Mobility is a key technology able to support many different business ideas, providing a comfortable seamless access to any services and any contents anywhere and anytime on the best possible devices

CISCO predicts that…

- Mobile data in 2014 will be 39 times larger than the one in 2009

- By the end of 2014, video will comprise66 percent of all mobile data traffic, andmobile voice traffic will comprise only 4percent of the overall total traffic

In 2G, 3G, and 3G+/4G,user (and host) mobility has been

a commodity in particular for voice services

LINK@KoreaTech 6

Short History:Mobility Service in Cellular Systems (1/5)

Source: [film] Cellular (2004)

Cellular operators now struggle to accommodate1) Much Internet data traffic &

2) Much signaling traffic for operational management

LINK@KoreaTech 7



LINK@KoreaTech 8


[Cellular Network Evolving to All-IP Network]– Various definitions for the next generation of mobile networks all align

around an “all-IP” vision, providing purely packet-switched capabilities and solely supporting IP services.

– Overall architectures of cellular and fixed networks convergeCustomer Premises Equipment (CPE) Digital Subscriber Line Access Multiplexer (DSLAM)

Broadband Network Gateway (BNG): the user’s IP Point of Attachment (PoA) to the

Internet

Enhanced Node B (ENB) base station: licensed cellular technology

Packet Data Network Gateway (PGW): IP PoA for the mobile subscriber Serving Gateway (SGW): Layer 2 tunnel switch

User Equipment (UE)

LINK@KoreaTech 9

Short History:Mobility Service in Cellular Systems (4/5) LTE (Long-Term Evolution)

– All-IP Version of Cellular and Fixed Network Convergence

Features of LTE from the perspective of Core Networks– 1) Simplified System Architecture– 2) Total Cost of Ownership (TCO) Reduced– 3) Service Continuity across Different Access Technologies

In fact, LTE is only the radio access network technology The core network architecture goes by the name System

Architecture Evolution (SAE) and defines the Evolved Packet Core (EPC), the fixed part of a mobile operator network

LTE

The radio access network tech.

SAE/EPC

The core network tech.

LTE: the representative term.

LINK@KoreaTech 10

Short History:Mobility Service in Cellular Systems (5/5)Mobile Network is evolving towards flat architecture

–Operator tends to simplify network–Flat architecture is beneficial to

• Operational cost reduction and Traffic offloading

–Content is likely to be distributed to edge network• CDN server is closer to edge network

There are multiple ‘add-on’ solutions with the multiple variants of ‘Mobile IP’

LINK@KoreaTech 11

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

Host-based IP Mobility

Network-basedIP Mobility

Mobility Support in IPv6[RFC 3775, June 2004]

Fast Handovers for Mobile IPv6[RFC 4068, July 2005]

Mobile IPv6 Support for Dual Stack Hosts and Routers

[RFC 5555, June 2009]

Multiple Care-of Addresses Registration

[RFC 5648, Oct. 2009]

Traffic Selectors for Flow Binding[RFC 6088, Jan. 2011]

Flow Bindings in Mobile IPv6 and NEMO Basic Support[RFC 6089, Jan. 2011]

Proxy Mobile IPv6[RFC 5213, Aug. 2008]

Fast Handovers for Proxy Mobile IPv6[RFC 5949, Sept. 2010]

IPv4 Support for Proxy Mobile IPv6[RFC 5844, May 2010]

Logical Interface Support for multi-mode IP Hosts[draft-ietf-netext-logical-interface-support-05.txt, April 2012]

Proxy Mobile IPv6 Extensions to Support Flow Mobility[draft-ietf-netext-pmipv6-flowmob-03, March 2012]

Short History:Mobility Solutions in Internet (IETF) (1/3)

Multiple variants of IETF Mobile IP

For some reason, they are not helping the world solve the problem

they were intended to solve. Why?

(Operators say…) “Why am I setting up a home agent?

Does this increase my revenue?”

LINK@KoreaTech 12


Then… Why? (Source: 83th IETF, March 2012)

LINK@KoreaTech 13

1. Competing solutions elsewhere in the system- 3GPP cellular networks - GTP Tunnel for IP Mobility- WLAN (IEEE 802.11) – Proprietary Solution (CISCO L2/L3 Switch)

2. Unclear motivations to provide the service- Without Mobile IP, most applications today have no trouble

3. They affects too many parts in the stack- They also need a kernel-level modification

4. They need to be distributed- Can users do P2P downloading via the home agent at 100 or 1000 Mbit/s?


1. Consider Mobility as the norm2. Support a massive number of always-on mobile devices

- Scalable and distributed mobility management solutions

3. Ubiquitous connectivity in heterogeneous access tech.- Data offloading to WLAN

LINK@KoreaTech 14

What Do We Need in Future Mobile Network/Internet?

Public Internet

Core Network

802.11/Hotspot

802.16e/WiMax

3G/4G Cellular

Access Router

Wireless Router

4. Service-oriented technology- Seamless access to a range of

mobile services, including video, peer-to-peer, VoIP, gaming and SNS services

- Mobile Social Network

5. Embrace new concept of mobile network architectures- Content Delivery/Centric Network (e.g., Soft-Bits Mobility)

- Generalized Delay Tolerant Network (DTN)(Data Ferry – Store & Carry & Forward Delivery)

- Sensor and Actuator Network (e.g., Networked Mobile Robots)

LINK@KoreaTech 15

What Do We Need in Future Mobile Network/Internet?


[Four Big Approaches]1. Distributed and Dynamic Mobility Management

- No centralized mobility agents and anchors- Data offloading with dynamic anchoring

2. Fast Store & Resolution with ID/LOC Separation - Distributed Hash Table

: (ID, LOC) pairs are stored and distributed in a DHT system

- Querying LOC & Tunneling/Translation

3. Storage-aware Routing- Store & Cache Hit

4. Mobile Social Network- Message Routing by using Social Network Analysis - Pocket Switch Network (PSN)

LINK@KoreaTech 16

Recent Mobility Management Technology

MNCN

DHT DHT

DHT

LTE/SAE Mobility Management

LINK@KoreaTech 17

LTE/SAE Architecture & Entities

LINK@KoreaTech 18

LTE Architecture & Entities

– User equipment (UE) is the mobile device– eNodeB is the access point– Mobile Management Entity (MME)

• authenticating the user (by interfacing with the HSS)• assigning temporary identifiers to the terminals• roaming authorization, and lawful intercept.

– Serving Gateway (Serving GW) • routes packets to and from other 3GPP networks (e.g., UMTS, GPRS) • a mobility anchor for the UE in those networks.


LINK@KoreaTech 19

LTE Architecture & Entities

– Packet Data Network Gateway (PDN GW) • the routing to and from non-3GPP networks (like Wi-Fi, Code Division

Multiple Access [CDMA] 1X, Evolution-Data-Optimized [EVDO], and WiMAX) • the permanent mobility anchor for the UE roaming with those networks—in

other words, the IP point of attachment.

– Home Subscriber Server (HSS) • contains the database with all subscriber data and is used to perform

authentication and authorization as well as to provide user location.


LINK@KoreaTech 20

LTE Architecture & Entities– From the inter-working perspective

LTE/SAE Identifiers

LINK@KoreaTech 21

International Mobile Subscriber Identity (IMSI)

– identifies users– conforms to the ITU E.164 numbering standard and is usually 15 digits

long– consists of…

• MCC (Mobile Country Code) • MNC (Mobile Network Code)• MSIN (Mobile Subscriber Identity)

– stored in the SIM card – used as the master key for subscriber data in the HSS– also used in 2G/3G networks

LINK@KoreaTech 22

Needs of Temporary subscriber identifiers– GUTI or S-TMSI– For privacy reasons, IMSI is sent as little as possible over the network.– They provide a mechanism to find the resources (i.e., MME) where the

subscriber’s temporary context is stored.– Pooling of MMEs

MME Pooling and Identifiers– Load balancing across MMEs

LTE/SAE Identifiers

LTE/SAE Identifiers

LINK@KoreaTech 23

Globally Unique Temporary ID (GUTI)

– A worldwide unique identity that points to a specific subscriber context in a specific MME.

– GUMMEI (Globally Unique MME Identifier)• MCC (Mobile Country Code) • MNC (Mobile Network Code) • MMEI (MME identifier, the MME within the network)

MMEGI (MME group ID) MMEC (MME Code)

– M-TMSI (MME Temporary Subscriber Identity)

LTE/SAE Identifiers

LINK@KoreaTech 24

Temporary Mobile Subscriber ID (S-TMSI)

– It is unique, only within a group of MMEs.– UE can use the S-TMSI when communicating with the network as long

as it stays within a TA that is part of the TA list it has received– GUTI is a long identifier and to save radio resources, a shorter version

of the GUTI is, called S-TMSI, used whenever possible. – S-TMSI is used for, for example, paging of UEs and service request

PDN Connectivity Service

With SAE/EPC, only the IP-based packet switched domain is available.

UE with multiple simultaneous PDN connections

LINK@KoreaTech 25


PDN Connectivity Service– Schematic view of application, PDN connection and transport layers

for LTE/SAE Architecture– PDN IP Connection

• Logical connection between a specific IPv4 address and/or IPv6 prefix allocated to a UE and a particular PDN

LINK@KoreaTech 26

PDN IP Connection (IP Point-to-Point Link)

IP Packet Routing


GPRS Tunneling Protocols (GTP)

– UDP (port 2152)-based tunnel protocol identified by a Tunnel Endpoint Identifier (TEID) and are used to carry encapsulated Tunneled Protocol Data Units (T-PDU).

– GTP-U• encapsulate “user data” between Serving-GW and PDN GW

– GTP-C• encapsulate “signal” between Serving-GW and PDN GW• support tunnel management operations (establishment/modifications/termination)

• support quality of service (QoS) negotiation.LINK@KoreaTech 27


GPRS Tunneling Protocols (GTP)

LINK@KoreaTech 28

ServingGW

PDNGW


IP address & Parameter Allocation– IP address for an UE to get access the connected PDN– Parameters needed for the IP stack to function correctly (e.g. DNS

address)– IPv4

• Option 1] Allocated by PDN GW during the attach procedure (E-UTRAN) • Option 2] Allocated by PDN GW during PDP context activation procedure

(GERAN/UTRAN)• Option 3] UE uses DHCPv4 to request an IP address after the attach (E-

UTRAN) or PDP context activation (GERAN/UTRAN)

– IPv6 • Only method] Stateless IPv6 address auto configuration

A /64 IPv6 prefix is allocated for each PDN connection and UE. No DAD (Duplicated Address Detection)

• GW sends an (unicast) IPv6 Router Advertisement (RA) to the UE after attach and PDP context activation are completed.

LINK@KoreaTech 29


Only GTP-based Architecture– EPS Bearer for GTP-based system

LINK@KoreaTech 30


GTP and PMIP-based Architecture– EPS Bearer for PMIP-based S5/S8 system

LINK@KoreaTech 31

Mobility Management

MM Classification– Location Management

• Location Update • Paging

– Handover Management• Inter-RAT Handover

Anchor Point: Serving GW

• Inter-Serving-GW Handover Anchor Point: PDN GW

• Inter Technology Handover

LINK@KoreaTech 32

Location Management at LTE

Location Update

– Cells are grouped into Tracking Areas (TAs)

• Every TA has a unique TA identity (TAI) which every eNB periodically broadcasts to an UE

– TAs are further grouped into TA Lists (TALs)– Location Update Procedure

• 1) UE stores the TAL that includes the TA where the UE resides TAL 1={TA 2, TA 3, TA 4}

• 2) UE listens to the broadcast TAI & checks if the received TAI is in its TAL • 3) If it is not in the current TAL, UE executes the location update procedure

to inform the MME of its TAL movement• 4) MME then assigns a new TAL to the UE

TAL 2={TA 4, TA 5, TA 6}

LINK@KoreaTech 33

R. Liou, Y. Lin, S. Tsai, “An Investigation on LTE Mobility Management,”IEEE Transactions on Mobile Computing, 2011


Location Update– [NOTE 1] TAL is assigned on a per-user basis

• i.e., TALs for different UEs may have different sizes and shapes

– [NOTE 2] New TAL may be overlapped with previous TAL• Central policy

MME assigns a new TAL whose central TA includes the cell where the UE enters

LINK@KoreaTech 34

TA

TAL


Location Update– Non-overlapping TALs

• Old 3GPP mechanism

– Overlapping TALs• Several proposals at academic papers• Eliminate the ping-pong effect

– Overlapping TAs with Per-user Basis & Central Policy– Commercially deployed at LTE

– LTE location update performance• Eliminate the ping-pong effect• outperforms 3G location update by 90% when the user wanders locally• incurs extra 4%-36% cost over 3G location update when the user tends to

move to one direction

LINK@KoreaTech 35


Paging– When an incoming call to the UE arrives, it may incur large paging

traffic if all cells in the TAL page the UE simultaneously. • 3GPP scheme: all cells in the TAL page

– To resolve this issue, three paging schemes can be considered• CT (Cell-TAL)

1) the last interacted cell 2) all cells in the TAL

• TT (TA-TAL) 1) TA of the last interacted cell 2) all cells in the TAL

LINK@KoreaTech 36


Paging– To resolve this issue, three paging schemes can be considered

• CTT (Cell-TA-TAL) 1) the last interacted cell 2) TA of the last interacted cell 3) all

cells in the TAL

– TAL-based paging scheme…• outperform 3G paging by 21%-97% in terms of the number of paged cells• Among three paging scheme…

CTT has the best performance for the most cases» but, the number of paging iterations is high

TT outperforms CT when the user movement pattern is regular CT outperforms TT when the user does not move frequently

LINK@KoreaTech 37


Paging Costs– Cp,x: the expected number of cells that page the UE when an incoming

call arrives, where x = {CT, TT, CTT}

LINK@KoreaTech 38

NC: the number of cells in a tracking area (TA)


Paging Costs– Cd,x: he expected number of paging iterations before the UE is found,

where x = {CT, TT, CTT}

LINK@KoreaTech 39

Handover Management at LTE

Basic Rule of LTE Handover for Service/Session Continuity– Network-based & Mobile Assisted Handover (MAHO)

Components of Handover Technology

LINK@KoreaTech 40


Issue 1 - Neighbor Discovery and Target Cell Selection – ANDSF (Access Network Discovery and Selection Function)

• A server that provides UEs with access networks as well as policies for access network selection.

• Based on the ANDSF information, the UE can understand… which network to scan for the operator policies with regard to handover –

» for example, whether to stay on 3GPP access or whether to perform the handover to another access network

– Target Selection• Policy based RRM• Positioning-aware selection• Utility function based Selection

LINK@KoreaTech 41


Issue 2 - IP Mobility Mode

– Possible handover combinations• 1) Intra and Inter 3GPP access handover

a. Intra E-UTRAN. b. E-UTRAN to/from GERAN/UTRAN (with “Only GTP” or “GTP & PMIP”). c. Intra GERAN, Intra UTRAN and GERAN to/from GERAN.

• 2) 3GPP and non-3GPP handover a. Optimized handover E-UTRAN to/from HRPD (with “Only GTP” or “GTP &

PMIP”). b. Non-optimized handover: trusted non-3GPP access to/from GERAN/UTRAN/E-

UTRAN (with GTP/PMIP on 3GPP access and PMIP/DSMIPv6 on non-3GPP access) c. Non-optimized handover: untrusted non-3GPP access to/from

GERAN/UTRAN/E-UTRAN (with GTP/PMIP on 3GPP access and PMIP/DSMIPv6 on non-3GPP access).

LINK@KoreaTech 42

3GPP Access Non-3GPP Access

Host-based - DSMIPv6 (or MIPv4)

Network-based Only GTP or GTP & PMIP PMIP* DSMIPv6: Dual-Stack Mobile IPv6


Inter-RAT Handover– Anchor Point: Serving GW

LINK@KoreaTech 43


Inter-Serving-GW Handover– Anchor Point: PDN GW

LINK@KoreaTech 44


Inter Technology Handover

LINK@KoreaTech 45

LMA

LMA

LMA: Local Mobility AnchorMAG: Mobile Access GatewayPBU: Proxy Binding UpdatePBA: Proxy Binding Ack.

[“Home in Any Place” with PMIP]- MAG sends the RA (Router Advertisement) messages advertising UE’s home network prefix and other parameters- MAG will emulate the home link on its access link. - UE always obtain its “home network prefix”, any where in the network. It will ensure that UE believes it is at its home.

EPC Architecture Options

Architecture Options

LINK@KoreaTech 46

Meng Wang, Michael Georgiades and Rahim Tafazolli, “Signalling Cost Evaluation of Mobility Management Schemes for different Core Network Architectural Arrangements in 3GPP LTE/SAE”IEEE VTC Spring, 2008

EPC Architecture Options

Signaling Costs for Different Architectural Options & MM Schemes– For calculating “Signaling Costs” the followings are considered

• Exchanged Signaling Procedures + Signaling Message Size

– Option 4 has best signaling cost, but heavy loads on the PDN GW– Option 2 & 3 have the best trade-off in total signaling cost and load on

each network node– Proxy MIPv6 has great advantage on reducing the signaling cost

LINK@KoreaTech 47

LTE_ACTIVE Mode LTE_IDLE Mode

Distributed and Dynamic Mobility Management(DMM)

LINK@KoreaTech 48

DMM Problem Statements

Limitations of Centralized Mobility Solutions1) Non-Optimal Routes

• Especially, CDN Server closer to the edge of the network.

2) Low Scalability• All nodes’ mobility context at HA (or LMA)• Heavy tunneling overhead

NOTE: most of users stay at a place • More and more traffic from and to mobile devices in the future

LINK@KoreaTech 49


Limitations of Centralized Mobility Solutions3) Non-Optimality in Evolved Network Architecture

• Traffic is increasing very fast in the era of Mobile Internet• Operator needs to lower the operation cost• Mobile Network is Evolving Towards Flat Architecture

4) Mobility Signaling Overhead • Mobility signaling overhead becomes significant, it is not expected

before.

LINK@KoreaTech 50


Limitations of Centralized Mobility Solutions5) “ALL” traffic’s concentration to the mobility anchor

• Currently, mobility support is performed per node, not per flow• It is impossible for some traffic to bypass the mobility anchor

6) Wasting Resources to Support Mobile Nodes Not Needing Mobility Support

• Two-thirds of a user mobility is local• It is needed to dynamically support mobility for a node

7) Single Point of Failure• Duplication or backup is needed

LINK@KoreaTech 51

Concepts of Distributed Mobility Management– Separating control and data planes

• splitting location and routing anchors.

– Distribution of the location (mobility mapping) servers– Placing the mobility management function closer to the edge of

the network (e.g. at the Access Router level)

LINK@KoreaTech 52

Distributed and Dynamic MM

Centralized(e.g., MIPv4, MIPv6, DSMIP, PMIPv6, GTP)

Fully Distributed (All location anchors co-locate with routing anchors)

Concepts of Distributed Mobility Management– Ideal View for DMM

LINK@KoreaTech 53

Distributed and Dynamic MM Concepts of Distributed Mobility Management

– Eliminate…• Tunneling between a single anchor point and an AR/an MN• Delay due to non-optimized routing• Single point of failure

Dynamic use of mobility support [refer to the next slide]

– allowing the split of data flows along different paths– Per-flow Address management needed

LINK@KoreaTech 54


Dynamic Distributed Approach

MAAR1

MN

CN

MAAR2

MAAR3

Pref1::Addr1

MAAR1

MN

CN

MAAR2

MAAR3

Pref2::Addr2

Pref1::Addr1

BU

BA

MAAR: Mobility Anchor and Access Router

LINK@KoreaTech 55


Flow 1

[Source: 82th IETF] Data Offloading with Dynamic Anchoring– PMIPv6-based Example

• Apps with long-term session selects… LMA anchored prefix (HNP::/64) E.g., VoIP, SSH Session, VPN Session

• Apps with short-term session selects… Local prefix (LOC::/64) topologically

under MAG’s control Traffic using local prefix bypasses LMA

» MAG does not tunnel it to the LMA

LINK@KoreaTech 56


[Source: 83th IETF]

[Source: 81th IETF]

LINK@KoreaTech 57

Distributed Hash Table at P2P Networks Distributed Hash Table (DHT) is a method to distribute “reference to

data” over a set of nodes DHT can balance load across all nodes

– all nodes manage roughly the same number of references

Three representative protocols for query routing and node join/departure:– Chord, Pastry, Kademlia

LINK@KoreaTech 58

DHT at Location Management

14 = hash (“abc”)

Binding Information

Analogy for Location Management– File is replaced with MN– Node: MN’s Attachment Point– key = hash (MN ID)– node = hash (IP address)– point (potential key or node)

MN ID = abc

Location Information Distribution• #Binding Information at “Central LR” vs. “Distributed LRs”

LINK@KoreaTech 59

• #MN: 500 (Randomly deployed)• #LRs: 1 (centralized), 2, 4, 8, 12• Simulation Scenario- Each MN is randomly deployed- Hash Function applied with MN ID (NAI)- Each MN’s Binding Info. distributed to each LR

Central LR Distributed LR (DLR)AR


0

100

200

300

400

500

600

AIMS LR=2 LR=4 LR=8 LR=12

# o

f Bin

din

gs

Central LR #DLR=2 #DLR=4 #DLR=8 #DLR=12

Used Hash Function:http://burtleburtle.net/bob/hash/doobs.html

DHT can be used for a method to distribute “location binding information” over a set of location registrars (LRs)

On the logical ring structure, each LR is initially assigned its ID by using the hash function

Each LR will store <Key: [MN-ID, Current Location]> tuples in its DHT structure.

LINK@KoreaTech 60


LR 0

0

4

26

5

1

3

7

keys1

keys2

keys

keys4

0

7

3

5

6

LR 1

LR 3

LR 6

Location Registration (Location Information Distribution)

LINK@KoreaTech 61


Location Registration(MN ID =

[email protected])

[email protected]

MAG#1

Default LRHome LR

H([email protected])=5

Registration Ack.

0

4

26

5

1

3

7keys

4

5

6

Connect

Registration Ack.Binding Info.

<[email protected], MAG#1>

(1)

(2)(3)

(4)(5)

(6)

(7) (8)

Location Query (Fast Resolution)

LINK@KoreaTech 62


[email protected]

MAG#1

Default LRHome LR

HADDR([email protected])=5

0

4

26

5

1

3

7keys

4

5

6

[email protected]

Default LR

MAG#2Send packets to [email protected]

Location Query(MN [email protected])Query Reply (MAG#1)

Send Packets

(1)

(2)

(3)

(4)

(5)

(6)

(7)

Binding Info.<[email protected],

MAG#1>

DMM Research at LTE/SAE

Distributed MME (proposed Bell Lab, 2011)

– Location management signaling processing distributed to dMME– UE Context (including location binding) stored ROS (Reliable Object

Storage)

LINK@KoreaTech 63

Xueli An, Fabio Pianese, Indra Widjaja, Utku Günay Acer, “DMME: Virtualizing LTE Mobility Management,”36th IEEE

Conference on Local Computer Networks, 2011

DMM Research at Future Internet

MobilityFirst project (NSF, 2010~2013)– Every mapping is replicated

at K random locations– Lookups can choose closest

among K mappings. – Much reduced lookup

latency

LINK@KoreaTech 64

DMM Standardization at IETF

DMM WG (Working Group)– The only mobility-related WG

• Past WGs related to Mobilty Mip4, Mip6, Netext (PMIPv6), Mext, Nemo, …

– BoF organized at 82th IETF (Taiwan, November 2011) – The first meeting at 83th IETF (Paris, March 2012)– Chairs

• Julien Laganier – Juniper Networks• Jouni Korhonen – Nokia Siemens Networks

– Scheduled Future Documents (RFCs)• DMM Solution Requirements• DMM Practices• Gap Analysis between DMM and Existing Solutions• DMM Solution Documents

– Homepage• http://datatracker.ietf.org/wg/dmm/• You can find 20 or more individual documents about DMM

LINK@KoreaTech 65

DMM References

Academic Papers– Introductory or Comprehensive Papers

• H Anthony Chan, Hidetoshi Yokota, Jiang Xie, Pierrick Seite, Dapeng Liu, “Distributed and Dynamic Mobility Management in Mobile Internet: Current Approaches and Issues,” Journal of Communications, Vol. 6, No. 1, PP. 4—15, Feb. 2011.

– Solution Papers (1/4)• Zhu, Z., Wakikawa, R., and L. Zhang, “SAIL: A Scalable Approach for Wide-

Area IP Mobility”, INFOCOM 2011 Mobiworld Workshop, April 2011.• H. Luo, Y. Qin, and H. Zhang, “A DHT-based Identifier-to-locator Mapping

Approach for a Scalable Internet,” IEEE Trans. Parallel Distrib. Syst., vol. 20, no. 12, pp. 1790–1802, 2009. S. Ratnasamy, P. Francis, M. Handley, R. Karp, and S. Shenker, “A Scalable

Content-Addressable Network,” Proc. ACM SIGCOMM’01, pp. 161-172, Aug. 2001.

• Y. Zhai, Y. Wang, I. You, J. Yuan, Y. Ren, X. Shan, "A DHT and MDP-based mobility management scheme for large-scale mobile internet," IEEE Infocom workshop-computer communication, April, 2011.

LINK@KoreaTech 66

DMM References

Academic Papers– Solution Papers (2/4)

• Y. Zhai, Y. Wang, J. Yuan, Y. Ren and X. Shan, "An Index Structure Framework to Analyze Host Mobility Supports for Integrated Networks," Journal of Networks, Vol. 4, No. 1, Feb. 2009.

• S. Zhuang et al., “Host Mobility Using an Internet Indirection Infrastructure,” ACM Wireless Networks, vol. 11, no. 6, Nov. 2005, pp. 741–56

• Y. Mao et al., “DHARMA: Distributed Home Agent for Robust Mobile Access,” Proc. IEEE INFOCOM 2005, Mar. 2005.

• H. Le, D. Hoang, A. Simmonds, B. Yousef, J. Chan, "An Efficient Mechanism for Mobility Support using Peer to Peer Overlay Networks," 3rd International IEEE Conference on Industrial Informatics, 2005.

• S. Pack, K. Park, T. Kwon and Y. Choi, "SAMP: Scalable Application-Layer Mobility Protocol," IEEE Communication Magazine, Vol. 44, No. 6, pp. 86-92, 2006. Ion Stoica, Robert Morris, David Karger, M. Frans Kaashoek, and Hari

Balakrishnan, Chord: A Scalable Peer-to-peer Lookup Service for Internet Applications, ACM SIGCOMM 2001, San Deigo, CA, August 2001, pp. 149-160.

LINK@KoreaTech 67

DMM References


• K.-H. Lee, H.-W. Lee, W. Ryu and Y.-H. Han, "A Scalable Network-based Mobility Management Framework in Heterogeneous IP-based Networks," Telecommunication System, Springer, DOI: 10.1007/s11235-011-9479-3, June 2011.

• S.-C. Lo and W.-T. Chen, "Peer-To-Peer Based Architecture for Mobility Management in Wireless Networks," 6th IFTP/IEEE Int Conf Mobile and Wireless Communication Networks, 2004

• K. Sethom, H. Afifi, G. Pujolle. "Palma: A P2P based Architecture for Location Management," 7th IFIP International Conference on Mobile and Wireless Communications Networks (MWCN 2005), Sep. 2005.

• A. M. Houyou, H. D. Meer, M. Esterhazy, "P2P-based Mobility Management for Heterogeneous Wireless Networks and Mesh Networks," In Proceedings of EuroNGI Workshop, 2005.

• S. C. Lo, “Mobility Management Using P2P Techniques in Wireless Networks,” Journal of Information Science and Engineering, vol. 23, no. 2, pp. 421–439, Mar. 2007.

LINK@KoreaTech 68

DMM References


• R. Farha, K. Khavari, N. Abji and A. Leon-garcia, "Peer-to-Peer Mobility Management for all-IP Networks," IEEE ICC’06, pp. 1946-1952, June 2006.

• R. Farha, K. Khavari, and A. Leon-garcia, "Peer-to-Peer Vertical Mobility Management," IEEE ICC’07, pp. 1846-1853, June 2007.

• R. Farha and A. Leon-garcia, "Peer-to-Peer Naming Architecture for Integrated Wireline/Wireless Networks," IEEE Globecom’07, pp. 2019-2024, Nov. 2007.

• H. Jung, M. Hohar, J.-I. Kim, S.-J. Koh, "Distributed Mobility Control in Proxy Mobile IPv6 Networks," IEICE Trans. on Comm. Vol. E94-B, No. 8, Aug. 2011.

• Jie Hou, Yaping Liu, Zhenghu Gong, “SILMS: A Scalable and Secure Identifier-to-Locator Mapping Service System Design for Future Internet,” The 2nd International Workshop on Computer Science and Engineering, 2009.

LINK@KoreaTech 69