21.11.2012 Views

Wireless Future - Telenor

Wireless Future - Telenor

Wireless Future - Telenor

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

mechanisms allow a handoff of a mobile node<br />

from one cell to another, re-establishing linklayer<br />

connectivity to the node in each new location.<br />

Within the natural limitations imposed by<br />

link-management solutions, and as long as such<br />

handoff occurs only within cells of the mobile<br />

node’s home link, such link-layer mobility<br />

mechanisms may offer faster convergence and<br />

lower overhead than Mobile IPv6. Extensions to<br />

the Mobile IPv6 protocol have been proposed to<br />

support a more local, hierarchical form of mobility<br />

management.<br />

3 Micro-mobility and Fast<br />

Handoff<br />

3.1 Background<br />

The design of Mobile IP is based on the assumption<br />

that the rate of movement between subnets<br />

is low. This leads to the fact that the protocol is<br />

not suited for micro-mobility support for which<br />

the change of IP subnet is assumed to be frequent.<br />

More specifically, the registration process<br />

requires that a new registration is sent to the<br />

Home Agent for every change of subnet. This<br />

registration process induces unnecessary high<br />

signalling load on the global Internet and high<br />

processing needs in the Home Agents. It also<br />

leads to unnecessary latency during handoff<br />

from one subnet to another.<br />

Several schemes have been proposed to solve<br />

the issue of micro-mobility management. All of<br />

these proposals assume a hierarchy in order to<br />

localise the scope of the mobility management to<br />

a domain (collection of subnet administrated by<br />

a single provider). Doing so reduces the global<br />

signalling traffic and enables a lower latency<br />

period during a change of subnet. These proposals<br />

assume Mobile IP for inter domain mobility<br />

and mainly focus on the intra domain mobility.<br />

There are two main concepts for managing the<br />

intra-domain mobility:<br />

The Host-based routing approach: Mobility<br />

management is distributed among all the nodes<br />

within the domain. Host-specific routing is<br />

employed to keep track of the current location of<br />

the Mobile Host (MH) within the domain. Special<br />

routers are thus needed. The address of the<br />

user is the care-of address assigned/authorised<br />

by the domain.<br />

The multiple Care-of Address approach: The<br />

Mobile Host is assigned multiple care-of<br />

addresses (COA), with each address identifying<br />

a specific agent/node in the hierarchy. Packets<br />

are routed through each node in the hierarchy<br />

using the corresponding care-of address. The<br />

Mobile Host only changes the care-of address of<br />

the lowest hierarchical level at every change of<br />

subnet. This approach uses conventional IP rout-<br />

Telektronikk 1.2001<br />

ing in the domain and distributes the mobility<br />

management over only a subset of nodes in the<br />

mobility domain.<br />

In the following we present these two concepts<br />

in more detail. We also review some of the proposed<br />

schemes and analyse their strong points<br />

and deficiencies. We note that at this point in<br />

time the schemes presented are in the form of<br />

Internet drafts and are thus under discussion in<br />

the IETF.<br />

3.2 Host based Routing Schemes<br />

3.2.1 Principles<br />

Many schemes belonging to the host based routing<br />

category have been proposed. The Cellular<br />

IP and Hawaii schemes have received most of<br />

the attention thus far. Figure 3-1 illustrates the<br />

basic functional architecture and the implied tree<br />

like network topology of the Hawaii and Cellular<br />

IP solutions. Both approaches create hostspecific<br />

entries through a specific path in the<br />

network topology. The ingress point into the<br />

domain is the root of the tree and is called the<br />

Gateway (GW) for Cellular IP and Domain Root<br />

Router (DRR) for the Hawaii scheme. Packets<br />

destined to the MH are forwarded through the<br />

sequence of nodes, the first one being the ingress<br />

point and the last one being the MH. It should be<br />

noticed that the edge device may not be a base<br />

station so that the schemes are applicable to<br />

solving mobility management in fix access networks<br />

as well. As an MH moves inside this<br />

Cellular IP/Hawaii<br />

Domain<br />

Internet<br />

GW/DRR<br />

Router* Router*<br />

Figure 3-1 Cellular IP<br />

and Hawaii architecture<br />

Router* Router* Router* Router*<br />

MH<br />

* Router with CIP or Hawaii Protocol<br />

87

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!