Multiplex communications – Communication over free space – Having a plurality of contiguous regions served by...
Reexamination Certificate
1999-12-07
2003-01-21
Le, Thanh Cong (Department: 2731)
Multiplex communications
Communication over free space
Having a plurality of contiguous regions served by...
C370S409000, C370S410000, C709S238000
Reexamination Certificate
active
06510144
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to Mobile IP network technology. More particularly, the present invention relates to Mobile IP inter- and intra-agent mobility.
2. Description of the Related Art
Mobile IP is a protocol which allows laptop computers or other mobile computer units (referred to as “Mobile Nodes” herein) to roam between various sub-networks at various locations—while maintaining Internet and/or WAN connectivity. Without Mobile IP or similar protocol, a Mobile Node would be unable to stay connected while roaming through various sub-networks. This is because the IP address required for any node to communicate over the Internet is location specific. Each IP address has a field that specifies the particular sub-network on which the node resides. If a user desires to take a computer which is normally attached to one subnetwork and roam with it so that it passes through different sub-networks, it cannot use its home base IP address. As a result, a business person traveling across the country cannot merely roam with his or her computer across geographically disparate network segments or wireless nodes while remaining connected over the Internet. This is not an acceptable state-of-affairs in the age of portable computational devices.
To address this problem, the Mobile IP protocol has been developed and implemented. An implementation of Mobile IP is described in RFC 2002 of the Network Working Group, C. Perkins, Ed., October 1996. Mobile IP is also described in the text “Mobile IP Unplugged” by J. Solomon, Prentice Hall. Both of these references are incorporated herein by reference in their entireties and for all purposes.
The Mobile IP process and environment are illustrated in FIG.
1
. As shown there, a Mobile IP environment
2
includes the Internet (or a WAN)
4
over which a Mobile Node
6
can communicate remotely via mediation by a Home Agent
8
and a Foreign Agent
10
. Typically, the Home Agent and Foreign Agent are routers or other network connection devices performing appropriate Mobile IP functions as implemented by software, hardware, and/or firmware. A particular Mobile Node (e.g., a laptop computer) plugged into its home network segment connects with the Internet through its designated Home Agent. When the Mobile Node roams, it communicates via the Internet through an available Foreign Agent. Presumably, there are many Foreign Agents available at geographically disparate locations to allow wide spread Internet connection via the Mobile IP protocol. Note that it is also possible for the Mobile Node to register directly with its Home Agent.
As shown in
FIG. 1
, Mobile Node
6
normally resides on (or is “based at”) a network segment
12
which allows its network entities to communicate over the Internet
4
using a standard router. Of course, this standard router may also implement Home Agent/Foreign Agent functionality when needed. Note that Home Agent
8
need not directly connect to the Internet. For example, as shown in
FIG. 1
, it may be connected through another router (a router R
1
in this case). Router R
1
may, in turn, connect one or more other routers (e.g., a router R
3
) with the Internet.
Now, suppose that Mobile Node
6
is removed from its home base network segment
12
and roams to a remote network segment
14
. Network segment
14
may include various other nodes such as a PC
16
. The nodes on network segment
14
communicate with the Internet through a router which doubles as Foreign Agent
10
. Mobile Node
6
may identify Foreign Agent
10
through various solicitations and advertisements which form part of the Mobile IP protocol. When Mobile Node
6
engages with network segment
14
, Foreign Agent
10
relays a registration request to Home Agent
8
(as indicated by the dotted line “Registration”). The Home and Foreign Agents may then negotiate the conditions of the Mobile Node's attachment to Foreign Agent
10
. For example, the attachment may be limited to a period of time, such as two hours. When the negotiation is successfully completed, Home Agent
8
updates an internal “mobility binding table” which specifies the care-of address (e.g., a collocated care-of address or the Foreign Agent's IP address) in association with the identity of Mobile Node
6
. Further, the Foreign Agent
10
updates an internal “visitor table” which specifies the Mobile Node address, Home Agent address, etc. In effect, the Mobile Node is given a new IP address to be able to receive and/or send information on segment
14
.
Now, suppose that Mobile Node
6
wishes to send a message to a corresponding node
18
from its new location. A message from the Mobile Node is then packetized and forwarded through Foreign Agent
10
over the Internet
4
and to corresponding node
18
(as indicated by the dotted line “packet from MN”) according to a standard Internet protocol. If corresponding node
18
wishes to send a message to Mobile Node—whether in reply to a message from the Mobile Node or for any other reason—it addresses that message to the IP address of Mobile Node
6
on sub-network
12
. The packets of that message are then forwarded over the Internet
4
and to router R
1
and ultimately to Home Agent
8
as indicated by the dotted line (“packet to MN(1)”). From its mobility binding table, Home Agent
8
recognizes that Mobile Node
6
is no longer attached to network segment
12
. It then encapsulates the packets from corresponding node
18
(which are addressed to Mobile Node
6
on network segment
12
) according to a Mobile IP protocol and forwards these encapsulated packets to a “care of” address for Mobile Node
6
as shown by the dotted line (“packet to MN(2)”). The care-of address may be, for example, the IP address of Foreign Agent
10
. Foreign Agent
10
then strips the encapsulation and forwards the message to Mobile Node
6
on sub-network
14
. The packet forwarding mechanism implemented by the Home and Foreign Agents is often referred to as “tunneling.”
As described above, a mobile node typically roams from its Home Agent on one router to a Foreign Agent on another router. When the mobile node disconnects from its Home Agent, a node that is sending packets to the mobile node will not receive an expected acknowledgement from the mobile node for a set of packets. As a result, the transmitting node will retransmit the set of packets to the mobile node through the Home Agent after a predefined period of time (or timeout period). This retransmission typically only occurs on a connection-oriented or reliable transport layer, such as TCP. If there is still no reply, the transmitting node attempts again to retransmit the set of packets, but after a longer predefined period of time. The transmitting node will keep trying to send the set of packets to the mobile node at ever increasing time intervals.
When the mobile node finally reconnects to a foreign agent and registers its new address (or reconnects to the same agent), the mobile node will have to wait a significant amount of time for packets to be resent by the transmitting node. That is, the mobile node must wait for the predefined time interval to expire before the transmitting node retransmits the packets.
In view of the above, it would be desirable to enable a mobile node to reestablish communication with a transmitting node after disconnecting from and reconnecting to such transmitting node without experiencing a significant delay in receiving packets.
SUMMARY OF THE INVENTION
Accordingly, the present invention provides an apparatus and method for triggering retransmission of packets that were sent by a sending node to a mobile node while the mobile node was temporarily cutoff from such sending node. In general terms, a portion of one or more packets and/or their associated headers is buffered as update information. This buffered update information can later be used to trigger retransmission of packets that were not received by a temporarily disconnected mobile node. This retransmission is triggered before the timeout period
Dommety Gopal K.
Laurens Roy
Leung Kent K.
Beyer Weaver & Thomas LLP.
Cisco Technology Inc.
Ewart James
Olynick, Esq. Mary R.
LandOfFree
Network layer support to enhance the transport layer... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Network layer support to enhance the transport layer..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Network layer support to enhance the transport layer... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3055212