[Seamoby] Revised Section 4 of CAR issues draft
"Hemant Chaskar" <hchaskar@hotmail.com> Wed, 16 January 2002 03:17 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19729 for <seamoby-archive@odin.ietf.org>; Tue, 15 Jan 2002 22:17:21 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA03645; Tue, 15 Jan 2002 21:58:02 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA03612 for <seamoby@optimus.ietf.org>; Tue, 15 Jan 2002 21:58:00 -0500 (EST)
Received: from hotmail.com (f264.law7.hotmail.com [216.33.236.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19542 for <seamoby@ietf.org>; Tue, 15 Jan 2002 21:57:57 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 15 Jan 2002 18:57:29 -0800
Received: from 63.78.179.5 by lw7fd.law7.hotmail.msn.com with HTTP; Wed, 16 Jan 2002 02:57:28 GMT
X-Originating-IP: [63.78.179.5]
From: Hemant Chaskar <hchaskar@hotmail.com>
To: seamoby@ietf.org
Date: Wed, 16 Jan 2002 02:57:28 -0000
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"
Message-ID: <F264SAfEqYv1judJhYn0001e0e3@hotmail.com>
X-OriginalArrivalTime: 16 Jan 2002 02:57:29.0372 (UTC) FILETIME=[891BF5C0:01C19E39]
Subject: [Seamoby] Revised Section 4 of CAR issues draft
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Hi,
Here is the revised text for Section 4 of CAR discovery issues draft. The
text has been finetuned. I hope that it is now clear enough. If there are no
more concerns on Section 4, we can submit the problem statement draft with
this text for Section 4, to IESG.
Hemant
-------------------------------snip----------------------------------
4. APPROACHES TO CANDIDATE ACCESS ROUTER DISCOVERY
In this section, we describe three approaches to CAR discovery,
namely the Anticipated CAR Discovery (discovery prior to handoff), Dynamic
CAR
Discovery (discovery at the time of handoff) and Hybrid CAR Discovery.
4.1 Anticipated CAR Discovery
In Anticpated CAR Discovery, CAR discovery is performed at some
point prior to the MN performing a handoff. This can be performed in
a number of ways and with various entities particpating in the process.
One illustrative method for Anticipated CAR Discovery is given below.
In this method, an AR currently serving an MN can identify a set of CARs for
the MN's handoff, at some point prior to handoff. This information is then
available at the time of handoff as input to the TAR Selection Algorithm.
Another
input to the TAR Selection Algorithm may be the preferences expressed by the
MN
prior to the handoff, or preferences enforced by the administrative control.
At
the time of handoff, it may only be required to provide input to the TAR
Selection
Algorithm about the reachability of neighboring ARs from the MN. This
reachability
information is usually in the form of the identity of the AP to which the MN
can listen to, and the current AR has to resolve this AP identity to the
GAAR's IP address.
The advantage of Anticipated CAR Discovery is that the handoff can be
executed
quickly because much of the information needed by the TAR Selection
Algorithm
is collected in advance of handoff.
Anticipated CAR Discovery is depicted in Figure 1.
-----------------------------------------------------------------
| All routers |
| | Discovery of ARs whose coverage |
| | areas overlap (GAARs) with that of |
| v the current AR |
| Local map of GAARs at current AR |
| | |
| | Capability identification |
| v |
| CARs for MN's handoff identified at current AR |
| | |
--------------------------|--------------------------------------
|
| Predefined preferences of the MN
AR Reachability | and administrative preferences
for the MN |
| | |
v v v
TAR Selection Algorithm executed at the time of
handoff to determine unique TAR for MN's handoff
Figure 1: Anticipated CAR Discovery
4.2 Dynamic CAR Discovery
In Dyanmic CAR discovery, CAR discovery is performed at the time the MN is
about to undergo handoff. Again, this can be performed in a number of ways
and with various entities particpating in the process. One illustrative
method
for Dynamic CAR Discovery is given below.
According to this method, an MN dynamically obtains information about the
available
ARs for handoff, along with their capabilities. This is done after the
handoff trigger
is generated. When the MN detects an AR that has capabilities matching its
preferences,
the MN may notify the currently serving AR to perform a handoff to this AR
using one or
more of the seamless handoff protocols. The advantage of this method is that
the MN
has fine-grained control over the TAR selection. However, this method
generates more
radio traffic during the CAR discovery step. This is because capability
information is
sent to the MN over the air. Also, it is required that the MN can receive
IP-level
capability information from the GAARs and negotiate requirements with the
GAARs, while
still being connected to the current AR.
Dynamic CAR Discovery is shown in Figure 2.
--------------------------------------------------------------
| |
| GAARs identified at handoff time |
| | |
| | Capability identification |
| | |
| v |
| CARs for MN's handoff identified |
| | |
---------------------------|----------------------------------
|
| TAR selection at the
| time of handoff
v
Unique TAR identity
Figure 2: Dynamic CAR Discovery
4.3 Hybrid CAR Discovery
In practice, a hybrid of the Anticipated and Dynamic CAR discovery
approaches
may be used. For example, in the hybrid approach, the GAAR discovery and
much
of the capability identification may be performed prior to handover, while
the
remaining capability identification may happen during the handover process.
But,
there are other alternatives too.
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] Revised Section 4 of CAR issues draft Hemant Chaskar
- RE: [Seamoby] Revised Section 4 of CAR issues dra… Hesham Soliman (ERA)
- RE: [Seamoby] Revised Section 4 of CAR issues dra… Govind Krishnamurthi