Mobile Network Layer

1
Mobile IP
 Systems like Global System for Mobile Communications(GSM) have

been designed with mobility in mind.

 The internet started at a time when no one had thought of mobile

computers.

 In this protocols and mechanisms developed for the network layer to

support mobility.

 It provides protocol enhancement that allows transparent routing of IP

datagram to mobile nodes in the internet.

 Mobile IP – Adds mobility support to the internet network layer protocol IP.

2
Cont..

 This is the reason for supporting mobility of that IP layer, mobile phone

system, for example, cannot after this type of mobility for heterogeneous

networks.

 To merge the world of mobile phone with the internet and to support mobility

in more efficiently, micro mobility protocol have been developed.

 Internet protocol (IP) is the common base for thousands of application and

runs over dozens of different networks .

 Mobile IP is an Internet engineering task Force(IETF) standard

communication protocol that is designed to allow mobile devices used to move

from one network to another with out changing their IP address

3
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)

4
Entities and Terminologies

 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 mobile node MN, typically a router

 registers the location of the mobile node, tunnels IP datagram to the Care-of Address

(COA)

 Foreign Agent (FA)

 system in the current foreign network of the MN, typically a router

 forwards the tunneled datagram to the MN, typically also the default router for the MN

5
Cont..

 Care-of Address (COA)

 Care-of Address – it defines the current location of the mobile node (MN)
from an IP point of view.
 All the packets sent to the MN are delivered to the COA, not directly to the IP address
of the MN
 Marks the tunnel endpoint (i.e address where packets exit the tunnel)

 Location of COA:-
 Foreign agent COA – COA could be located at the FA, i.e COA is an IP address of the
FA.
 Co-located COA – if the MN temporarily acquired an additional IP
address which acts a COA. This address is topologically correct , and the tunnel endpoint
is at MN.

 Correspondent Node (CN)

 A partner through which mobile node is connected. It can be a fixed or mobile node.

6
Cont..

Fig 6.1 Mobile IP entities and terminologies

7
IP packet delivery
 In this process Correspondent Node (CN) wants to send an IP packet
to the mobile node (MN).
 Internet , not having info on the current location of MN, routes the
packet to the router(Home Agent) responsible for the home network of
MN.
 HA now intercept the packet(to find current location)
 Not found in home n/w then encapsulated and tunneled to the COA.
 A new header put in front of the old header showing the (FA) COA as
the new destination.
 FA now decapsulates the packets (remove additional header)
 Last, MN sends the packets as usual with its own fixed IP address as
source and CN's address as the destination.

8
Cont..

Fig 6.2 Data transfer from the mobile system

9
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)

10
Cont..

11
 Cont..
 ICMP part
 Type – 9
 Code – 0 or 16
 #addresses – no. of
addresses advertised with
this packet
 Lifetime – length of time
this advr. is valid
 Preference – most eager
router to get new node
12
Cont..
Extension part – for mobility
 Type – 16
 Length – depends on no. of
COAs provided with the msg.
 Seq. No
 Reg. Lifetime – max. lifetime in
sec. a node can request during
reg.
 R – reg. , B – busy , H – HA , F
– FA ,
 M & G – method of
encapsulation , V - version
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.

13
Registration

 It is 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
 Objective – is to inform the HA of the current location for correct
forwarding of packets
 After receiving COA address the MN has to register with the HA.
 Registration can be done in two ways:- Registration of mobile node via
the FA Or , directly with the HA

14
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.

15
Cont..

Fig 6.3 Registration request message

16
Cont…
 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 is used.

 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. and Mobile-home authentication extension – to prevent remote redirect
attack.
17
Cont..

Fig 6.4 fields in registration request as set by mobile node

18
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
19
Cont…

Fig 6.5 registration reply

20
Tunneling and Encapsulation
 Tunneling
 Establishes a virtual pipe for data packets between a tunnel entry and a tunnel
endpoint.
 It is mechanisms used for forwarding packets between the HA and COA.
 Packets entering a tunnel are forwarded inside the tunnel and leave the
 tunnel unchanged.
 Tunneling is achieved by using encapsulation.

 Fig 6.6 tunneling processs

21
Cont…
 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
 Outer header: the new header
 IP-in-IP-encapsulation, minimal encapsulation or GRE (Generic Record
Encapsulation)

Fig 6.7 encabsulation

22
Introduction to mobile Ad hoc networks
 Ad Hoc network is an autonomous system of mobile hosts(MHs)
(also serving as routers) connected by wireless links.”
 It does not need support from any existing infrastructure, like
Base Station, Access Point, etc.
 An ad hoc (also written ad-hoc or ad hoc) network is a local
network with wireless or temporary plug-in connection, in
which mobile or portable devices are part
of the network only while they are in close proximity.
 Example In military group of soldiers in close proximity sharing
information on their notebook computers using RF signals
 A mobile node that is an end host and not a router. A Mobile
Host is capable of sending and receiving packets.

23
Mobile ad hoc network (MANET)

 A mobile ad hoc network (MANET) is an autonomous system

of mobile nodes, mobile hosts (MHs), or MSs (also serving as
routers) connected by wireless links, the union of which forms
a network modeled in the form of an arbitrary communication
graph.

 MANETs are basically peer-to-peer (p2p) multihop mobile

wireless networks where information packets are transmitted
in a store-and-forward method from source to destination, via
intermediate nodes.

24
Cont…

• Fig 6.8 Ad hoc and infrastructure model

25
Mobile ad hoc Network protocols
 MANET routing protocols need to adapt to changes in the network
topology and maintain routing information, so that packets can be
forwarded to their destinations.
 Although MANET routing protocols are mainly for mobile networks,
they can also be useful for networks of stationary nodes that lack
network infrastructure.
 They are classified as Proactive, reactive, and hybrid routing protocols
are all forms of ad hoc routing.

26
Mobile ad hoc Network protocols
 Reactive routing protocol: also known as on-demand routing protocol, it finds a
path when nodes choose to send data to a specific location .

 These protocols do not start route exploration until the source node is ready to
send a packet to the destination.

 This type of routing protocol includes protocols that are grouped together. The
well-known reactive routing protocols are AODV (Ad-hoc On-Demand Distance
Vector) and DSR (Dynamic Source Routing).

 Routing protocols that are proactive (Table driven) propagate the network,
update routes at predetermined intervals and attempt to maintain consistent,
progressive routing information between any pair of nodes in the network.

 Since the information for routing is stored in tables, these protocols are often
referred to as table-driven protocols.

27
Mobile ad hoc Network protocols
 It includes protocols including the Destination-Sequenced Distance-Vector
(DSDV), Wireless Routing Protocol (WRP), Optimized Connection State
Routing Protocol (OLSR), and Fisheye State Routing, among others
(FSR).

 Hybrid protocols combine proactive and reactive routing protocols. Some

hybrid routing protocols have been suggested, which combine the benefits
of proactive and reactive routing protocols.

 Zone routing protocol is the most common hybrid protocol (ZRP).

 Zone-Based Hierarchical Link State (ZHLS) and key extraction

distributed ad hoc routing are two more hybrid routing protocols
(CEDAR).

28
 I AM
YO CHA
UU P TE
ND R SI X
ER
STA . D
ND O
ME

29