Multimedia Network Lab.

Mobile Computing

Chapter 8:
Mobile Network Layer

Prof. Sang-Jo Yoo

http://multinet.inha.ac.kr
http://multinet.inha.ac.kr The Graduate School of Information Technology and Telecommunications,
Telecommunications, INHA University

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Contents
‰ Mobile IP overview
‰ Agent discovery
‰ Registration
‰ Tunneling
‰ DHCP
‰ Mobile IP multicasting

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 2
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Motivation for Mobile IP

‰ Routing
‹ based on IP destination address, network prefix (e.g. 129.13.42)
determines physical subnet
‹ To avoid an explosion of routing tables, only prefixes are stored aand
further optimizations are applied.
‹ change of physical subnet implies change of IP address to have a
topological correct address (standard IP) or needs special entries in the
routing tables

‰ Specific routes to end-systems?

‹ change of all routing table entries to forward packets to the right
destination
‹ does not scale with the number of mobile hosts and frequent changes in
the location, security problems

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 3

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Motivation for Mobile IP

‰ Changing the IP-address?
‹ adjust the host IP address depending on the current location
„ Assigning a new IP address (DHCP)
‹ Problem: nobody knows about this new address.
‹ Almost impossible to find a mobile system, DNS updates take to long time
‹ TCP connections break, security problems
„ TCP connection = {source IP, source port, destination IP, destination port}
„ TCP connection cannot survive any address change.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 4
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Requirements to Mobile IP
‰ Transparency
‹ Mobility should remain ‘invisible’ for many higher layer protocols and
applications
‹ For TCP, mobile computer must keep its IP address.
‰ Compatibility
‹ support of the same layer 2 protocols as IP
‹ no changes to current end-systems and routers required
‹ mobile end-systems can communicate with fixed systems
‰ Security
‹ The minimum requirement: all the messages related to the management
of Mobile IP are authenticated.
‰ Efficiency and scalability
‹ Only little additional messages to the mobile system required (connection
typically via a low bandwidth radio link)

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 5

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Terminology
‰ Mobile Node (MN)
‹ system (node) that can change the point of connection
to the network without changing its IP address
‰ Home Agent (HA)
‹ system in the home network of the MN, typically a router
‹ registers the location of the MN, tunnels IP datagrams to the COA
‰ Foreign Agent (FA)
‹ system in the current foreign network of the MN, typically a router
‹ forwards the tunneled datagrams to the MN, typically also the
default router for the MN
‰ Care-of Address (COA)
‹ address of the current tunnel end-point for the MN (at FA or MN)
‹ actual location of the MN from an IP point of view
‰ Correspondent Node (CN)
‹ communication partner

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 6
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Terminology
Care-of Address (COA)

‰ Foreign agent COA

‹ The COA could be located at the FA (IP address of FA)
‹ The FA is the tunnel end-point and forwards packets to the MN.
‹ Many MN using the FA can share this COA.

‰ Co-located COA
‹ MN temporarily acquired an additional IP address which acts as COA.
‹ Tunnel end-point is at the MN.
‹ Co-located care-of address can be acquired using services such as DHCP

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 7

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Example network
HA
MN

router

home network mobile end-system

Internet
(physical home network
for the MN)
FA foreign
network
router
(current physical network
for the MN)
CN

end-system router

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 8
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Data transfer to the mobile system

HA
2
MN

home network receiver

Internet
3

FA foreign
network

1. Sender sends to the IP address of MN,

HA intercepts packet (proxy ARP)
1 2. HA tunnels packet to COA, here FA,
CN
by encapsulation
3. FA forwards the packet
sender to the MN

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 9

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Data transfer from the mobile system

HA
1 MN

home network sender

Internet

FA foreign
network

1. Sender sends to the IP address

CN of the receiver as usual,
FA works as default router
receiver

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 10
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Overview
COA

home router router

MN
network HA FA

foreign
Internet network

CN router

3.
home router router
2. MN
network HA FA
4.
foreign
Internet network

1.
CN router

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 11

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Mobile IP Design Goals

‰ A mobile node must be able to communicate with other nodes after
changing it’s link-layer attachment, yet without changing its IP
address
‰ A mobile node must be able to communicate with other nodes that do
not implement mobile IP
‰ Mobile IP must use authentication to offer security against
redirectment attacks
‰ The number of administrative messages should be small to save
bandwidth & power
‰ Mobile IP must impose no additional constraints on the assignment of
IP addresses

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 12
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Protocol Overview
‰ Advertisement
‹ HA and FA periodically send advertisement messages into their physical
subnets
‹ MN listens to these messages and detects, if it is in the home or a foreign
network MN reads a COA from the FA advertisement messages
‹ A mobile node can solicit for mobility agents

‰ Registration - when a mobile node is away from home, it must

register its care-of address with it’s home agent
‹ these actions have to be secured by authentication

‰ Delivering Datagrams
‹ Datagrams must be forwarded by the Home Agent to the Foreign Agent
for delivery to the care-of address.
‹ The delivery mechanism must handle all packets (including broadcast and
multicast)
‹ A tunnel is used for this

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 13

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Overall Behaviors

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 14
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

1. Agent Discovery
‰ Problems:
‹ How to find a foreign agent?
‹ How does the MN discover that it has moved?
Æ Agent advertisement and Agent solicitation

‰ Agent advertisement
‹ HA and FA advertise their presence periodically using Agent
advertisement messages
‹ ICMP (Internet Control Message Protocol) message with some mobility
extensions : RFC 1256
„ IP header: TTL=1
destination IP: 224.0.0.1 (multicasting), 255.255.255.255(broadcasting)

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 15

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Agent advertisement
0 7 8 15 16 23 24 31
Type=9 Code checksum
#addresses addr. size lifetime
router address 1
preference level 1
router address 2
type = 16 preference level 2
length = 6 + 4 * #COAs
...
Lifetime: max lifetime in seconds
a node can request
R: registration required type = 16 length sequence number
B: busy, no more registrations registration lifetime R B H F M G r T reserved
H: home agent COA 1
COA 2
F: foreign agent
M: minimal encapsulation ...
G: GRE encapsulation
r: =0, ignored (former Van Jacobson compression)
T: FA supports reverse tunneling
reserved: =0, ignored

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 16
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Agent Solicitation
‰ MN can send Agent solicitation message
‹ If no agent advertisement are present,
‹ The inter-arrival time of agent advertisements is too high, or
‹ The MN just power on.
‹ Based on RFC 1256, ICMP router solicitation message

‰ Move detection
‹ Move detection using lifetime
„ If a MN fails to hear an advertisement from the foreign agent (or home agent)
with the specified Lifetime.
„ The MN can assume that it has moved to a different link, waits Agent
Advertisement or sends Agent Solicitation.
‹ Move detection using network-prefixes
„ If the network-prefix of the received Agent Advertisement is different from the
that of the previous foreign agent, then registration process should be invoked.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 17

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

2. Registration
‰ Request forwarding services when visiting a foreign network
‹ This allocates a local (foreign) node address
‰ Inform home agent of their current care-of address
‹ This creates a binding of the foreign node address to the home address
‰ Renew a binding that’s about to expire
‹ Bindings have lifetimes
‰ De-register when they return home

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 18
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Registration and Security

‰ The home node and the mobile node have conducted some form of
prior key exchange
‹ This defines a “secret” between the two nodes
‹ The authentication mechanism must defend against replay attacks

‰ A replay attack occurs when a 3rd party can capture your packets and
then “replay” them, fooling you into thinking they are correctly
authenticated.
‹ E.g., sending an encrypted password over a network leaves you open to a
replay attack. Note that attack didn’t decrypt.
‹ Nonces: Each message from A -> B includes a new random number.
When B replies to A, it must include that same random number. Likewise,
each B->A message includes a new random number generated by B and
echoed by A.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 19

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Registration Request
‰ Registration Request Message
‹ The message is sent to FA when foreign agent care-of address is used or
R bit of Advertisement is set.
‹ The message is directly sent to HA when collocated care-of address is
used .
MN re FA HA
g is
requ tration
e st MN re HA
regi gist
s requ ra t ion
requ tration est
est

on
g i strati trati
on
re g i s
y re
repl repl
y
tion
stra
regi
y
repl t

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 20
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Registration Request

• Both send to
UDP
port 434.
(Registration
Reply also)
• IP source
address:
interface
address of the
MN
• IP destination
address:
•HA: when
co-located
care-of
address is
used
•FA: when
FA care-of
address
The Graduate is of Information Technology and Telecommunications,
School Telecommunications, INHA University 21
used

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Registration Request
‹ Type =1
‹ S – set to 1 to ask that its HA create or delete a binding for the
specified care-of address.
‹ B – to tell the HA to encapsulate broadcast datagrams from
home network to the care-of address.
‹ D – to inform the HA where the exit-point of the tunnel is
located.
‹ Lifetime – the number of seconds it would like its registration to
last before it expires.
‹ Home address
‹ Home agent address
‹ Care-of address
‹ Identification – 64 bits for replay protection.
‹ Mobile-home authentication extension – to prevent remote
redirect attack.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 22
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Registration Request

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 23

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Registration Reply
‹ Lifetime:tells the mobile node how long the registration will be honored by the HA.
„ It can be shorter than requested, but never longer.

registration successful
0 registration accepted
1 registration accepted, but simultaneous mobility bindings unsupported
registration denied by FA
65 administratively prohibited
66 insufficient resources
67 mobile node failed authentication
68 home agent failed authentication
69 requested Lifetime too long
registration denied by HA
129 administratively prohibited
131 mobile node failed authentication
133 registration Identification mismatch
135 too many simultaneous mobility bindings

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 24
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

3. Tunneling
‰ Tunnel
‹ Establishes a virtual pipe for data packets between a tunnel entry and a
tunnel endpoint.
‹ Tunneling is achieved by using encapsulation

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 25

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Encapsulation
‰ Encapsulation
‹ Mechanism of taking a packet consisting of packet header and data and
putting it into the data part of a new packet.
‹ Decapsulation: reverse operation
‹ Outerheader: the new header
‹ IP-in-IP-encapsulation, minimal encapsulation or GRE (Generic Record
Encapsulation)

original IP header original data

new IP header new data

outer header inner header original data

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 26
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Encapsulation (IP-in-IP)
‰ IP-in-IP-encapsulation (mandatory, RFC 2003)
‹ tunnel between HA and COA

ver. IHL DS (TOS) length

IP identification flags fragment offset
TTL IP-in-IP IP checksum
IP address of HA
Care-of address COA
ver. IHL DS (TOS) length
IP identification flags fragment offset
TTL lay. 4 prot. IP checksum
IP address of CN
IP address of MN
TCP/UDP/ ... payload

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 27

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Encapsulation (IP-in-IP)
‰ The outer IP header source & destination address identify the tunnel
endpoints (e.g., HA & FA).
‰ Outer protocol is ‘4’ (IP protocol)
‹ Indicates payload is also IP datagram (version 4)

‰ The inner IP header source address and destination address identify

the original sender & recipient
‹ Not changed by the encapsulator, except to change TTL
‹ TTL is changed to 1 (why?)

‰ Other headers for authentication might be added to outer header.

‰ Some outer IP header fields are copied from the inner IP fields (TOS),
most are re-computed (TTL, checksum, length) based on new
datagram

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 28
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Encapsulation (Minimal)
‰ Minimal encapsulation (optional)
‹ avoids repetition of identical fields
‹ e.g. TTL, IHL, version, DS (RFC 2474, old: TOS)
‹ only applicable for unfragmented packets, no space left for fragment
identification

ver. IHL DS (TOS) length

IP identification flags fragment offset
TTL min. encap. IP checksum
IP address of HA
care-of address COA
lay. 4 protoc. S reserved IP checksum
IP address of MN
original sender IP address (if S=1)
TCP/UDP/ ... payload

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 29

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Generic Routing Encapsulation

original
original data
header

GRE original
outer header original data
header header

RFC 1701
new header new data
ver. IHL DS (TOS) length
IP identification flags fragment offset
TTL GRE IP checksum
IP address of HA RFC 2784
Care-of address COA
CR K S s rec. rsv. ver. protocol C reserved0 ver. protocol
checksum (optional) offset (optional) checksum (optional) reserved1 (=0)
key (optional)
sequence number (optional)
routing (optional)
ver. IHL DS (TOS) length
IP identification flags fragment offset
TTL lay. 4 prot. IP checksum
IP address of CN
IP address of MN

TCP/UDP/ ... payload

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 30
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Optimization of packet forwarding

‰ Triangular Routing
‹ sender sends all packets via HA to MN HA FA

‹ higher latency and network load

‰ “Solutions”
‹ sender learns the current location of MN Source Node
‹ direct tunneling to this location
‹ HA informs a sender about the location of MN
‹ big security problems!
‰ Change of FA
‹ packets on-the-fly during the change can be lost
‹ new FA informs old FA to avoid packet loss, old FA now forwards
remaining packets to new FA
‹ this information also enables the old FA to release resources for the MN

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 31

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Change of foreign agent

CN HA FAold FAnew MN

Data Data Data

Update
ACK

Data Data
MN changes
location
Update Registration Registration
ACK to HA is not
Data shown
Data Data
Warning
Smooth
Request Handover
Update
ACK
Data
Data
t

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 32
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Reverse tunneling
HA
2
MN

home network sender

Internet
1
FA foreign
network

1. MN sends to FA
3 2. FA tunnels packets to HA
CN by encapsulation
3. HA forwards the packet to the
receiver receiver (standard case)

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 33

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Mobile IP with reverse tunneling

‰ Router accept often only “topological correct“ addresses (firewall!)
‹ a packet from the MN encapsulated by the FA is now topological correct
‹ furthermore multicast and TTL problems solved (TTL in the home network
correct, but MN is to far away from the receiver)
‰ Reverse tunneling does not solve
‹ problems with firewalls, the reverse tunnel can be abused to circumvent
security mechanisms (tunnel hijacking)
‹ optimization of data paths, i.e. packets will be forwarded through the
tunnel via the HA to a sender (double triangular routing)
‰ The standard is backwards compatible
‹ the extensions can be implemented easily and cooperate with current
implementations without these extensions
‹ Agent Advertisements can carry requests for reverse tunneling

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 34
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Soft Tunnel State

‰ Relaying ICMP (Internet Control Message Protocol) [RFC 792]
Messages

tunnel

HA FA MN1

ICMP error message MN2

???
ICMP message is sent to the tunnel entry-point (HA).
How to relay the message and to whom?

Source2 Source1

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 35

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Soft Tunnel State

‰ Tunnel entry-point necessary to relay certain ICMP messages to the
original source.
‰ HA maintains soft state per each tunnel.
‹ Path MTU
‹ The number of hops
‹ Whether or not the end of tunnel is reachable.

‰ HA updates its soft state based upon ICMP messages received from
routers within the tunnel.
‹ If the received ICMP message is “fragmentation needed”, then increase
path MTU.
‹ If HA receives the ICMP “time exceeded”, then increase the length of the
tunnel.
‹ If HA receives “destination unreachable”, then it knows that the tunnel is
now un reachable.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 36
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Soft Tunnel State

‰ When HA receives a IP datagram, check the soft state of the tunnel
that will be used.
‹ If the tunnel has a problem, then
‹ Send a ICMP message to the source without sending the datagram to the
destination.

‰ Why do we call the information as “soft state”?

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 37

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Proxy and Gratuitous ARP

‰ Hosts remaining on the home network sends IP packets to the link
with MN’s MAC address that is stored in ARP cache.

‰ So, HA must perform proxy ARP for the mobile node.

MN

HA

MAC frame
S MN
ARP cache

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 38
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Proxy and Gratuitous ARP

‰ HA broadcasts gratuitous ARPs to the hosts on the link as soon as the
MN moves away form the home network
‹ Every node updates its ARP cache.
„ IP home address of the MN ↔ MAC address of the HA
‰ When MN returns to the home network, HA broadcast gratuitous ARPs
„ IP home address of the MN ↔ MAC address of the MN

HA
1. ARP

2. to HA
S MN
ARP cache

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 39

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Mobile IP and IPv6

‰ Mobile IP was developed for IPv4, but IPv6 simplifies the protocols
‹ security is integrated and not an add-on, authentication of registration is
included
‹ COA can be assigned via auto-configuration (DHCPv6 is one candidate),
every node has address autoconfiguration
‹ no need for a separate FA, all routers perform router advertisement
which can be used instead of the special agent advertisement; addresses
are always co-located
‹ MN can signal a sender directly the COA, sending via HA not needed in
this case (automatic path optimization)
‹ “soft“ hand-over, i.e. without packet loss, between two subnets is
supported
„ MN sends the new COA to its old router
„ the old router encapsulates all incoming packets for the MN and forwards them
to the new COA
„ authentication is always granted

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 40
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Problems with mobile IP

‰ Security
‹ authentication with FA problematic, for the FA typically belongs to another
organization
‹ no protocol for key management and key distribution has been
standardized in the Internet
‰ Firewalls
‹ typically mobile IP cannot be used together with firewalls, special set-ups
are needed (such as reverse tunneling)
‰ QoS
‹ many new reservations in case of RSVP
‹ tunneling makes it hard to give a flow of packets a special treatment
needed for the QoS
‰ Security, firewalls, QoS etc. are topics of current research and
discussions!

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 41

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

IP version 6 (Mobile IP)

Mobile IPv4 Mobile IPv6
Mobile node, home agent, home link, (same)
foreign link
Mobile node’s home address Globally routable home address and link-
local home address
Foreign agent A “plain” IPv6 router on the foreign
link(foreign agent no longer exists)
Foreign agent care-of address All care-of addresses are collocated
Collocated care-of address
Care-of address obtained via Agent Care-of address obtained via Stateless
Discovery,DHCP, or manually Address autoconfiguration, DHCP, or
manually

Agent Discovery Router Discovery

registration with home agent notification of home agent and other
correspondents

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 42
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

4. IP Micro-mobility support

‰ Limitation of traditional Mobile IP

‹ Mobile IP can result in disruption to user traffic during handoff.

‹ Mobile IP has high control overhead due to frequent notification to the
HA.
‹ On every handoff, new QoS reservation would be reestablished from
the HA to the FA even though most of the path remains unchanged.
‹ Thus,Mobile IP has some limitation when applied to wide-area wireless
networks with high mobility users that may require QoS.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 43

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

IP Micro-mobility support
‰ Micro-mobility support:
‹ Efficient local handover inside a foreign domain without involving a home
agent
‹ Reduces control traffic on backbone
‹ Especially needed in case of route optimization

‰ Example approaches:
‹ Cellular IP
‹ HAWAII
‹ Hierarchical Mobile IP (HMIP)

‰ Important criteria:
Security Efficiency, Scalability, Transparency, Manageability

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 44
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Mobility Classification
‰ Micro-mobility is the movement of an MN within or across different
BSs within a subnet and occurs very rapidly. (local mobility)

‰ Macro-mobility is the movement of an MN across different subnet

within a single domain or region,and occurs relatively less
frequently. (intradomain mobility)

‰ Global Mobility is the movement of an MN among different

administrative domains or geographical regions. (interdomain
mobility)

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 45

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Cellular IP
‰ Operation:
‹ “CIP Nodes“ maintain routing Internet
entries (soft state) for MNs
‹ Multiple entries possible Mobile IP
‹ Routing entries updated based on
packets sent by MN CIP Gateway
data/control
‰ CIP Gateway: packets
‹ Mobile IP tunnel endpoint from MN 1
‹ Initial registration processing

BS BS BS
packets from
MN2 to MN 1

MN1 MN2

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 46
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Cellular IP(Routing)
‰ Cellular IP gateway periodically broadcasts a beacon packet that is
flooded in the access network.
‰ Base station records the neighbor they last received this beacon
from and use it to route packets toward gateway.
‰ All packets transmitted by mobile hosts, regardless of their
destination address, are routed toward the gateway using these
routes.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 47

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Cellular IP(Routing)
R(X,BS1)
Gateway,
R
care of address BS2 (X,BS3)
BS1(X,BS2)

BS3
Data packet are transmitted by MH
Data packet are destined to MH X
Beacon packet Mobile Host X

‰ As these packets pass each node en route to the gateway,their route

information is recorded as follows
‰ Each base station maintains a routing cache.
‰ Soft state mapping remains valid for a system-specific time called route-
time-out.
‰ As long as mobile host X regularly sends data packet,base station along the
path between Gateway and Mobile Host X
‰ To keep its routing cache mappings valid,the mobile host transmit route-
update packets on the uplink at regular intervals called route- updated time

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 48
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Cellular IP(Handoff)
‰ Cellular IP hard handoff is based on a simple approach that trade
off some packet loss for minimizing handoff signaling rather than
try to guarantee zero packet loss.
‰ Cellular IP semisoft handoff exploits the notion that some mobile
hosts can simultaneously receive packets from the new and old
base stations during handoff.
‰ Semisoft handoff minimizes packet loss,providing improved TCP
and UDP performance over hard handoff.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 49

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Cellular IP(Hard Handoff)

‰ To perform handoff,a mobile host tunes its radio to a new base

station and sends route-update packet.
‰ In the case of hard handoff handoff latency is equal to the
round-trip time between mobile host and crossover BS. (In the
worst case the crossover BS is the gateway.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 50
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Cellular IP(Semisoft Handoff)

‰ Semi-soft handoff scales well for large number of mobile hosts and
frequent handoff.
‰ Semi-soft handoff comprises two architectural components.
‹ In order to reduce handoff latency,the routing cache mappings
associated with the new base station must be created before the actual
handoff takes place.
‹ In order to resolve unsynchronized packet,mapping created at
crossover points by the reception of semisoft packets include a flag to
indicate that downlink packets must pass through a delay device
before being forwarded for transmission along the new path.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 51

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

HAWAII
‰ Handoff-Aware Wireless Access
Internet Infrastructure Internet
HA
‰ Operation:
‹ MN obtains co-located COA 1 Backbone
and registers with HA 2
Router
‹ Handover: MN keeps COA,
new BS answers Reg. Request 3
and updates routers 4 Crossover
‹ MN views BS as foreign agent Router
2
‰ Security provisions: 4 Mobile IP
‹ MN-FA authentication mandatory DHCP
‹ Challenge/Response Extensions BS BS BS
Server
mandatory Mobile IP
3
MN MN DHCP
1

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 52
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

Hierarchical Mobile IPv6 (HMIPv6)

‰ Operation:
‹ Network contains mobility anchor point Internet
(MAP) HA
„ mapping of regional COA (RCOA) to link COA
RCOA
(LCOA)
‹ Upon handover, MN informs MAP
MAP only
„ gets new LCOA, keeps RCOA
‹ HA is only contacted if MAP binding AR AR
changes update
LCOAnew LCOAold

MN MN

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 53

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

5. DHCP: Dynamic Host Configuration Protocol

‰ Application
‹ If a new computer is connected to a network, DHCP provide it with all
necessary information for full system integration into the network.
‹ supplies systems with all necessary information, such as IP address, DNS
server address, domain name, subnet mask, default router etc.
‹ enables automatic integration of systems into an Intranet or the Internet,
can be used to acquire a COA for Mobile IP
‰ Client/Server-Model
‹ the client sends via a MAC broadcast a request to the DHCP server: DHCP
Discover. DHCPDISCOVER

DHCPDISCOVER
server client

client relay

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 54
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

DHCP - protocol mechanisms

server client server
(not selected) initialization (selected)
DHCPDISCOVER DHCPDISCOVER
determine the determine the
configuration configuration
DHCPOFFER DHCPOFFER
List of configuration
collection of replies parameters
time

selection of configuration
DHCPREQUEST DHCPREQUEST
(reject) (options) confirmation of
configuration
DHCPACK
initialization completed

release
DHCPRELEASE delete context

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 55

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

DHCP characteristics
‰ Server
‹ several servers can be configured for DHCP, coordination not yet
standardized (i.e., manual configuration)
‰ Renewal of configurations
‹ IP addresses have to be requested periodically, simplified protocol
‰ Options
‹ available for routers, subnet mask, NTP (network time protocol)
timeserver, SLP (service location protocol) directory,
DNS (domain name system)

‰ Big security problems!

‹ no authentication of DHCP information specified

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 56
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

6. Mobile IP multicasting problem

definition
IETF Standards Correspond Node

‰ Remote-subscription
‹ Optimal routing (con) Internetwork

‹ Frequent multicasting tree updating (pro)

‹ Join delay (pro)
FA(HA) FA
Move

‹ Out-of-synch problem (pro)

Mobile Host Mobile Host

‰ Bidirectional-tunneling
‹ No out-of-synch problem (con)
Correspond Node
‹ No tree updating and join procedure (con)
‹ Multiple unicast tunnels from a HA to a FA (pro) Internetwork

‹ Multiple tunnels from different HAs to a FA (pro)

‹ No optimal routing (pro) FA(HA) FA
Membership Add
Move

‹ Registration delay
Mobile Host Mobile Host

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 57

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

Mobile IP Multicasting
‰ MOM (ACM Mobicom’97)
‹ Use bidirectional tunneling
‹ Solve tunneling convergence problem
‹ Select one HA from multiple HAs in FA for a group: DMSP

DMSP
HA HA HA HA HA HA

FA FA

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 58
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

‹ DMSP selection methods

„ Age-based, count-based
‹ DMSP handoff events
„ MHs of DMSP movement
„ New MH comes in

‹ Problems of MOM
„ No optimal routing (still exists)
„ Out-of-synch problem (newly generated)
„ Registration delay for tunneling (still exists)
„ Losses during DMSP handoff (newly generated)

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 59

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

‰ RBMOM (IEICE Trans. on Comm. 2001)

‹ Hybrid: bidirectional tunneling & remote subscription
‹ Method
„ D=distance between FA and MHA
„ Dh=distance between FA and HA
„ MHA: multicast agent for a MH (HA or FA)
„ R=predetermined threshold distance (hop count)
When a MH moves to a new FA
If (D > R)
if (Dh<=R)
if(FA is on the multicast tree)
MHA=FA
else MHA=HA
else
MHA=FA
if FA is not on the tree, then join the tree
inform to HA that FA is now MHA for the MH
inform to the previous MHA that it does not need to send data.
Else
inform to the MHA the location of the new FA
(RBMOM can use DMSP approach on selecting MHA)

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 60
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

‰ Problems of RBMOM
‹ It does not consider reliable multicasting
‹ Data structure and operational procedures for all agent types are
not perfect.
‹ Distance between FA and MHA is not only thing to decide for
joining the tree.
‹ HA is receiving the multicasting data (as a member of the tree)
even though there is no MH that is receiving data from the HA.

‰ RBMOM modification (IEE Electronics Letters, 2002)

‹ Service range R (distance from MHA to the new FA) is dynamically
decided by MHA
„ So, tunneling or joining the tree is decided by MHA not FA
„ R*(1hop delay)+TDs-mha+Ttunnel<=maxDelay
TDs-mha=(hops from S to MHA)*(1hop delay)
Ttunnel= tunneling process delay

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 61

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

‰ MMROP (IEEE Trans. on Consumer Electronics, 2001)

‹ Basically, use IETF-RS method
‹ To solve out-of-synch problem, missing sequence packets are
transmitted by tunnel between new FA and old FA.

‹ Problems
„ It still has many problems of RS

join

2) leave[4,6]
FA FA FA
3) 4.5.6
1) 7.8.9

1.2.3

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 62
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

REMMIP
‰ Objectives
‹ Tunneling from MA (multicast agent, HA or FA) instead of HA.
„ FA can be a MA for the MH that visited before.
„ Reduce path length from source to MH.
„ Reduce packet loss and out-of-synch problem
‹ Eliminate HAs from multicasting tree
„ If it does not have any MHs in its home network and it does not act as MA for other FAs.
‹ Reliable and efficient mobile IP multicasting mechanism.

‰ MA
‹ HA maintains the MH’s location.
‹ MA is the agent that has a responsibility to send multicast data to a certain FA.
‹ MA should join the multicast tree.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 63

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

1. MH moves to new FA
‹ MH sends the GroupInfo when it initiates normal mobile IP registration
procedure.
‹ IF the new FA does not receives data of the group.
„ The MH is the first host of the group.
„ FA sends TUNNELING REQUEST[SEQmh+1] to the MA of the MH
„ FA sets the MH’s MA to the FA’s MA
„ IF there is out-of-synch problem, FA requests RECOVERY REQUEST [SEQmh+1,
SEQma-1] to the MH’s prev agent.
„ Optionally, MH can send MOVE message to the MH’s prev agent.

S
HA Normal MIP GroupInfo
registration
Group ID
MA Address
1
MA FA Prev Agent Address
2 3 Registration
1. TR[SEQmh+1] HA Address
FA 4 (GroupInfo)
2. Data transmission
3. RR[a,b] Sequence Number
4. Recovery data SEQmh

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 64
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

‹ IF the new FA has already received data from other MA.

„ FA selects a MA from the possible MA candidates (current and new).
¾ MA changes cause out-of-synch problem for the existing MHs, so it is not
recommended.
¾ MA selection events
• When a new MA candidate is added.
¾ Many MA selection methods can be considered.

„ IF the MA of the FA is not changed.

¾ Notify (MA CHANGE) to the new MH.
¾ IF FA cannot send all data [SEQmh+1,SEQfa] to the new MH, FA requests
RR [SEQmh+1, SEQfalast-1] to the MH’s prev Agent.
• After FA received the data, it forwards them to the new MH.
¾ Optionally, the new MH can send MOVE message to the MH’s prev agent.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 65

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

S prev
new 9.STOP
MA
MA 7.RR
6.data
SEQfa 8.data
5.TR
FA 1. MC
2. RR
4
FA 3. data

prev
SEQmh
„ IF FA selects a new MA(MH’s MA).
¾ Notify (MA CHANGE) to all MHs except the new MH in FA network that MA has been
changed.
¾ FA sets the new MA as its MA.
¾ IF FA cannot send all data [SEQmh+1,SEQfa] to the new MH, FA requests RR
[SEQmh+1, SEQfalast-1] to the MH’s prev Agent.
• After FA received the data, it forwards them to the new MH.
¾ FA sends TUNNELING REQUEST[SEQfa+1] to the new MA.
¾ IF there is out-of-synch problem, FA sends RR[SEQfa+1, SEQma-1] to the FA’s prev MA.
¾ FA sends STOP to the FA’s prev MA.
¾ FA sends reordered data to all MHs in the network..
¾ Optionally, the new MH can send MOVE message to the MH’s prev agent.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 66
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

2. BT to RS by FA
‹ When FA is not on the tree and uses BT, if one of the following
conditions is satisfied, then join the multicasting tree.

1) #MH > Th(N)

If the number of MHs is greater than threshold value – many customers: optimal
routing
2) min(MHt)>Th(T)
If the minimum staying time of MHs is greater than threshold value – slow mobility
3) Hop(DMSP-FA)>Th(H)
If the number of hops from DMSP to FA is greater than threshold value – reduce
hop count

2) Join
3) 7.8.9
MA 1)1.2.3 4) MA=FA
6) STOP[4,6] FA
5) MA CHANGE(MA=FA)
7) 4.5.6
8) 4.5.6.7.8.9

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 67

http://multinet.inha.ac.kr Multimedia Network Lab.

Lab.

3. IF agent(HA, FA) recognizes MH’s leaving.

‹ All agents can know MH’s leaving
„ Soft state: MH and/or agent periodically transmits membership
message.
„ Explicit MOVE message is sent by MH.
‹ IF there exists no MH of a multicast group.
‹ TEHN
‹ Case 1: MA of the agent = Agent (the agent joined tree)
„ Check there is any FA that is served by the agent.
„ IF no, wait a moment (because of RECOVERY REQUEST)
¾ Leave from the multicast tree.
S
PRUNE

STOP FA STOP
FA FA
or HA
All hosts moved.

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 68
 http://multinet.inha.ac.kr Multimedia Network Lab.
Lab.

‹ Case 2: MA of the agent! =Agent (the agent is served by other agent)

„ Wait a moment (because of RECOVERY REQUEST)
„ Send STOP to the agent’s MA to finish tunneling.

FA STOP
MA
or HA
All hosts moved.

MA Address If the agent joined the tree,

then MA=Agent address
Prev MA Address

Group ID SEQ(agent)

Served FA Lists Only if the agent joined the tree

MH Lists MHs that are in the agent network
Group ID

The Graduate School of Information Technology and Telecommunications,

Telecommunications, INHA University 69