Global IP Mobility Management

2007. 8. 21. Sangjin Jeong ETRI Future Internet Camp 2007 <sjjeong@etri.re.kr>

Transition of network infrastructure

Wired core network and wireless access network Majority of nodes are laptop type (large computing capability)
Access network H/O

Internet

Increasing number of wireless access networks (sensor networks) and roaming over various access networks Lightweight handheld mobile nodes or sensors with minimal IP stack
Access net

Internet
Access net

Mobility support scenarios (e.g., health care)

Several sensors are attached on a patient. The sensors monitor patients body status and send the gathered data to sink node for further processing (e.g., emergency warning) Main characteristics
Single, low- to medium-sized star networks Moving in an infrastructure of sink nodes Automatic configuration for mobility support Periodic data gathering

(From:draft-ekim-6lowpan-scenarios-00)
3

Mobility support scenarios (e.g., battle field)

Soldiers or tanks are equipped with small devices (e.g., battle information delivering system) and roams over battle field

Main characteristics
Mobility support Possibly dense node populations Highly mobile networks Cross various access networks
4

Considerations for mobility support

Due to the low computational performance of lightweight mobile nodes, the mobile nodes are not or minimally involved in mobility management signaling
Security (authorizing peers, channel security) or multihoming seems to be tough issues to tackle

Dormant/low battery powered node consideration

Lightweight nodes tend to have low battery power It is necessary to optimize power consumption in small devices Dormant nodes are minimally or not to be interfered by mobility management signaling

Mobility support irrespective of mobile node capability will be essential functionality for future network infrastructure

Needs for alternative approach to mobility support in the Internet

During the last decade, mobile IP has been the primary solution for IP mobility support protocol in the Internet Host-based Mobile IPv4/v6 has not been yet deployed that much
Heavy burden for a small device to have full implementation of Mobile IP
RFC 3344 (MIPv4): 99 pages RFC 3775 (MIPv6): 165 pages

Battery problem Waste of air resource

Therefore, it is necessary to develop a new mechanism so as to support IP mobility in the Internet (networkbased mobility management)
6

Network-based IP mobility management solutions

Mobile IPv6 and Mobile IPv4 are the enabler for IP mobility
Mobile IP client functionality in the mobile nodes stack There exist a number of mobile nodes without Mobile IP functionality It is desirable to support IP mobility for all hosts irrespective of the presence or absence of mobile IP functionality in the IP stack

Existing network-based IP mobility management solutions relocate Mobile IP signaling to network entities (intermediate nodes)
Signaling type Network type

IPv6 Proxy Mobile IPv6 X

IPv4 Proxy Mobile IPv6 IPv4 Extension Proxy Mobile IPv4

Mobile IPv6 Mobile IPv4

Advantages to using network-based mobility management

Support nodes without any mobility management protocol Avoid tunneling overhead over the air
7

Approach for global IP mobility management

Mobile nodes w/o mobility management protocols can roam over global Internet or can cross different access networks
Heavy burden for lightweight mobile nodes to do MM signaling

Easy to support both IPv6 and IPv4 nodes

Current GMM protocols (MIPv4, MIPv6) are not easy to simultaneously support both IPv4 and IPv6 nodes

ISPs may not want hierarchical two-level mobility

MIP for GMM, PMIP for LMM

It is desirable to leverage current network-based IP mobility management solution to global IP mobility management Scope of global mobility management
Global MM : MM handling movements on a global basis (i.e. handover between administrative domains) Local MM : MM handling movements in a local basis (or limited area) (i.e. within single administrative domain)
8

Requirements for network-based global IP mobility management

Default data path CN

Context transfer (Info. about MN)

HA1 HA2

Access Network1

Route optimization Handover policy (security, service, accounting, )

Access Network2 AR3

AR1

AR2

Handover MN
9

MN

Discussion
Will mobility be one of key drivers for future network?
There exist a lot of scenarios and applications that require mobility support

It is expected that network-based IP mobility support solution will facilitate the deployment of IP mobility in local network
Reuse deployed infrastructure & Mobile IPv6 functionality Favorable to ISPs Can network-based mobility support solution also be a candidate for mobility management protocol in the future internet?

Network-based global IP mobility management

Major hurdle is security association between differently administrative access networks

10

References
Design and Application Spaces for 6LoWPANs, draftekim-6lowpan-scenarios-00.txt Proxy Mobile IPv6, draft-ietf-netlmm-proxymip6-01.txt IPv4 Support for Proxy Mobile IPv6, draft-ietf-netlmmpmip6-ipv4-support-01.txt WiMAX Forum/3GPP2 Proxy Mobile IPv4, draft-leungmip4-proxy-mode-03.txt

11