19CSE342

Wireless and Mobile Communication

Mobile IP

J.Govindarajan
 Agenda
• Optimization
• Requirements
- IP-in-IP Encapsulation
• Entities and Terminologies - Minimal Encapsulation
• IP Packet Delivery - Generic Routing Encapsulation
• Reverse Tunneling
• Agent Discovery
– Agent Advertisement
• IPv6
– Agent Solicitation • IP-Micro Mobility Support
- Cellular IP
• Registration - Hawall
• Tunneling and Encapsulation - Hierarchical Mobile IPv6
 Traditional IP Packet Delivery to Mobile Device (destination)

160.5.10.0/16
IP Packet
Dst: 200.8.4.20 R1
R3

R4
Source
IP Address : IP Packet
150.10.2.5
Dst: 200.8.4.20
Transmission is 200.8.4.20/16
R5 Successful
IP Packet IP Packet
Segment Dst: 200.8.4.20 Dst: 200.8.4.20
IP header IP Packet Destination IP Address :
200.8.4.20
 Traditional IP Packet Delivery to Mobile Device (destination):
Address has changed : Packet Drop
160.5.10.0/16
IP Packet
Dst: 200.8.4.20 R1
R3

M Destination IP Address :
R4 o 160.5.10.5
Source
IP Address : IP Packet Destination is not v
150.10.2.5 available: Drop the e
Dst: 200.8.4.20 packet d 200.8.4.20/16
R5
IP Packet
Segment Dst: 200.8.4.20
IP header
 Requirements : Mobile Device
• To enable mobility in the internet

• Mobility should remain invisible to the higher layer protocols (Example: TCP)
– High layers (Example :TCP) should continue to work even if the mobile computer has
changed its point of attachment

• Remain compatible with all lower layers

• Enhancing IP for mobility with minimal overhead in message exchange and

flooding.
 Mobile IP
current location of the MN
Care-Of-Address

Mobile
node
Home Agent Foreign Agent

COA types:
FA COA
Co-located COA

MN - Mobile node
CN - Corresponding Node
HA - Home Agent
Correspondent Node FA - Foreign Agent
Mobile IP : Data delivery to and from mobile node
 Agent discovery
1) Agent Advertisement
type=9
code=0, if the agent also routes traffic from non-mobile nodes,
code=16, if it does not route anything other than mobile traffic

Standard ICMP advertisement

R bit (registration)
B-Busy to accept the registration
H-Home Agent
F-Foreign Agent
M-Minimal Encapsulation
G-Generic Encapsulation
r-0 (ignored)
T-Reverse Tunnelling is supported by FA
ICMP advertisement - Mobility

type=9
length=6 + 4*(number of addresses)
mobile node can send out three solicitations, one per second, as soon as it enters a new
2) Agent solicitation: network.
 Registration
S bit an MN can specify if it wants the HA to retain
prior mobility bindings
B bit -MN also wants to receive the broadcast
packets of Home Network
D bit-decapsulation by MN if co-located COA
M-Minimal Encapsulation
G-Generic Encapsulation Registration request
r and x-0 (ignored)

Registration If the COA is co-located

Registration If the COA is at the FA

Inform the HA of the current location for correct
forwarding of pack
Registration Reply

ICMP type =3
 Tunneling and encapsulation

Encapsulation
 IP-in-IP
encapsulation
 Minimal
encapsulation
Generic Routing
encapsulation
Protocol fields for GRE
according to RFC 1701

Protocol fields for GRE

according to RFC 2784
 Optimizations

Change of the foreign

agent with an optimized
mobile IP
 Reverse tunneling
• Need for reverse tunneling
– Firewalls
– Multi-cast
– TTL

• Reverse tunneling creates triangle problem in reverse direction

• Security problems related to reverse tunnelling need to be
resolved.
Micro mobility vs Macro mobility
Mobile IP/Cellular IP Architecture
IP Micro-mobility
IP Micro-mobility : Cellular IP
 HAWAII
Architecture of HAWAII
(Handoff-Aware Wireless Access Internet
Infrastructure,
Protocol)
Hierarchical Mobile IP (MIPv6 )

Mobility Anchor Point

access routers
 IPv6 and Mobility
• Features of IPv6:
• Stateless address autoconfiguration
• Optional NAT (Network Address Translation)
• Easier administration with DHCPv6
• Improved quality of service with flow labeling
• IP address Format
 IPv6 address

• Aggregatable Global Address

• Link-Local Address

• IPv4-Compatible IPv6 Address

• Unique Local Address

 Aggregatable Global Address
• Aggregatable global addresses are used on links that are
aggregated upward through organizations, and eventually to
the Internet service providers (ISPs).
Link-Local Address
IPv4-Compatible IPv6 Address
Unique Local Address
 IPv6 and Mobile IP
• Every mobile node is able to create or obtain a topologically correct address for the current
point of attachment.
• Every IPv6 node can send binding updates to another node, so the MN can send its current COA
directly to the CN and HA.
• A soft handover is possible with IPv6.

• The FA is not needed any more.

• CN only has to be able to process binding updates, i.e., to create or to update an entry in the
routing cache
• The MN itself has to be able to decapsulate packets, to detect when it needs a new COA, and to
determine when to send binding updates to the HA and CN. A HA must be able to encapsulate
DHCP