US 7,072,323 B2Grant
System and method for performing soft handoff in a wireless data network
Issue Date:2006-07-04
•33 Claims
•10 Drawing Sheets
Abstract
A communications network which is capable of effectively and efficiently handling mobility of wireless user terminals between access point nodes of a packet-switched network with minimal overhead and packet loss, and a method for using the same. The communications network employs a packet-switched core network and a plurality of access points coupled to the core network. Each access point is adapted to provide any user terminal with wireless communications access to the core network when that user terminal becomes affiliated with that access point. The system and method further employ ad-hoc routing techniques during handoff of a wireless user terminal between access point nodes of the core network to enable the network to maintain multiple paths via which data packets are provided to the user terminal during handoff to substantially eliminate packet loss during handoff.
Metadata
Assignee
- MeshNetworks, Inc.
Inventors
- Robin U. Roberts
- Charles R. Barker, Jr.
Application Information
Application Number:US 09/929,031
Filing Date:2001-08-15
Priority Date:2001-08-15
Art Unit:2664
Classifications
IPC:
H04Q7/24
Patent Drawings (10 sheets)
Description
Cross-Reference to Related Applications
[0001] Related subject matter is disclosed in a U.S. patent application of Charles R. Barker, Jr. and Robin U. Roberts entitled “A System and Method for Providing an Addressing and Proxy Scheme for Facilitating Mobility of Wireless Nodes Between Wired Access Points on a Core Network of a Communications Network”, application Ser. No. 09/929,032 filed on even date herewith, the entire contents of which is incorporated herein by reference.
Background of the Invention
[0002] 1. Field of the Invention
[0003] The present invention relates to an improved system and method for performing soft handoff between access points of a wireless communications network. More particularly, the present invention relates to a system and method for performing soft handoff using ad-hoc routing and multiple access points of a packet-switched communications network.
[0004] 2. Description of the Related Art:
[0005] Wireless communications networks, such as mobile wireless telephone networks, have become increasingly prevalent over the past decade. These wireless communications networks are commonly referred to as “cellular networks”, because the network infrastructure is arranged to divide the service area into a plurality of regions called “cells”.
[0006] Specifically, a terrestrial cellular network includes a plurality of interconnected base stations that are distributed geographically at designated locations throughout the service area. Each base station includes one or more transceivers that are capable of transmitting and receiving electromagnetic signals, such as radio frequency (RF) communications signals, to and from user terminals, such as wireless telephones, located in its coverage area. The communications signals include, for example, voice data that has been modulated according to a desired modulation technique and transmitted as data packets. As can be appreciated by one skilled in the art, the transceiver and user terminals transmit and receive the data packets in multiplexed format, such as time-division multiple access (TDMA) format, code-division multiple access (CDMA) format, or frequency-division multiple access (FDMA) format, which enables a single transceiver at the base station to communicate simultaneously with several user terminals in its coverage area.
[0007] Because each base station can only handle a limited amount of communications signal traffic from the user terminals at any given time, the coverage area of a base station can vary depending on the amount of traffic that the base station is expected to experience. For example, the coverage area of a base station can be set to several miles in diameter in sparsely populated regions, such as rural regions having light wireless traffic, and can be set to less than a mile in diameter in densely populated regions, such as major metropolitan areas having heavy wireless traffic. The wireless communications network therefore must employ many base stations in heavily populated metropolitan areas in order for the network to adequately service the user terminals in those regions.
[0008] Each base station is also connected to one or more gateways that enable communication between the base station and other networks, such as the Internet and the public switched telephone network (PSTN). Accordingly, the base stations in the network enable the user terminals to communicate with each other, as well as with other destinations, such as telephony devices, in the PSTN.
[0009] Since wireless user terminals are typically mobile, it is common for a user terminal to travel between different base station coverage areas during use. When this occurs, the base station whose coverage area the user terminal is leaving must transfer or “handoff” the user terminal to the base station whose coverage area the user terminal is entering, so that the latter base station can become the base station via which the user terminal and network continue to communicate. In densely populated areas having many base stations with small coverage areas, this handoff process may need to occur several times during a short period of time as the user terminal travels between the different coverage areas.
[0010] Many techniques have been developed using the circuit-switched cellular infrastructure to minimize data packet loss during handoff while also minimizing overhead necessary to successfully perform the handoff. For example, a technique known as “hard handoff” refers to a break-before-make technique where the original connection is dropped before the new connection is established. On the other hand, “soft handoff” is a make-before-break technique that maintains multiple simultaneous connections to the user terminal during handoff, and only drops the original connection after the new connection is established. Examples of soft handoff techniques are described in a publication by Wong et al. entitled “Soft Handoffs in CDMA Mobile Systems”, IEEE Personal Communications, December 1997, pp. 6–17, in a publication by Wong et al. entitled “A Pattern Recognition System for Handoff Algorithms”, IEEE Journal on Selected Areas in Communications, Vol. 18, No. 7, July 2000, pp. 1301–1312, and in TIA document TIA/EIA-95-B entitled “Mobile Station-Base Station Compatibility Standard for Wideband Spread Spectrum Cellular Systems”, Feb. 1, 1999, the entire contents of each of these documents being incorporated herein by reference.
[0011] With the arrival of the Internet in recent years, some wireless communications networks have moved away from the use of conventional cellular networks and their associated circuit switched routing techniques to improve voice communications services. Each mobile user terminal, telephony device, and any other device capable of communicating with the communications network, has a unique Internet Protocol (IP) address that uniquely identifies it from all other devices. A communications network employing IP sends data between destination points in digital form in discrete packets, rather than in the traditional circuit-committed protocols of the PSTN. Each of the data packets includes the sender's IP address as well as the intended receiver's IP address.
[0012] When a wireless user terminal, for example, transmits voice data to a base station of the communications network acting as the access point for the user terminal, a router associated with the base station reads the receiver IP address in the data packet. Each router includes a table of routing information, such as IP addresses of the devices local to the router, available routes, and so on. If the router recognizes from the receiver IP address that the data packet is intended for a telephony device in its immediate neighborhood or domain, the router forwards the data packet to that telephony device. However, if the router does not recognize the IP address as belonging to such a telephony device, the router forwards the data packet to an appropriate adjacent gateway in, for example, the Internet. The router of that gateway then reads the receiver IP address in the data packet, and either delivers the data packet to the appropriate telephony device in its domain, or forwards the data packet to another gateway. Once a router in a gateway recognizes the receiver IP address as belonging to a telephony device in its domain, the router in that gateway delivers the data packet to that telephony device.
[0013] It can be also noted that the use of IP to route data packets in a communications network enables the network to handle data other than voice data. For example, such IP techniques can be used to expand the versatility of the network to communicate audio, video or multimedia data between user terminals.
[0014] As in traditional cellular communications networks, wireless user terminals in a wireless communications network employing IP can be mobile, and can thus periodically change their access point to the network. Also, wireless user terminals can move outside their “home” network and become temporarily affiliated with a foreign network, and thus communicate via an access point on that foreign network.
[0015] Existing mobile data communications networks using IP techniques are based around conventional circuit-switched cellular infrastructures as discussed above, and therefore mask packet routing issues internal to their own networks. That is, when a user terminal moves its affiliation from one access point or base station to another within the network, the network can perform handoff techniques similar to those performed by a conventional wireless cellular network.
[0016] However, when a user terminal moves away from its home network and becomes affiliated with an access point on a foreign network, such topology changes must be communicated between routers in the home and foreign networks, so that the routers can update their respective routing tables as necessary, which results in substantial bandwidth-consuming overhead. Accordingly, it is generally agreed that this solution is too slow to handle user terminals that may be constantly mobile between networks, because routing changes must be propagated across the entirety of the connected network.
[0017] Another technique to handle the mobility of user terminals between networks without performing router updates is referred to as Mobile IP. A detailed description of Mobile IP is set forth in IETF document RFC 2002 entitled “IP Mobility Support”, October 1996, the entire content of which is incorporated herein by reference. In accordance with the Mobile IP technique, a fixed access point on the mobile user terminal's home network, which can be referred to as a fixed network node, functions as a proxy agent (MIP home agent) for the mobile user terminal (mobile node) when the mobile node moves out of the home network and becomes affiliated with an access point (foreign node) on a foreign network. As understood in the Mobile IP art, the home network is the network at which the mobile node seems reachable to the rest of the Internet or to other networks by virtue of the mobile node's assigned IP address (home address), and a foreign network is the network to which the mobile node is attached when it is not attached to its home network.
[0018] Accordingly, when data packets are transmitted from another device to the mobile node, the Mobile IP home agent receives those data packets on the core home network behalf of the mobile node, and encapsulates those data packets. That is, the Mobile IP home agent incorporates each received IP data packet, less any preceding fields such as a media access control (MAC) header, inside another IP data packet, thereby making the fields within the original IP header of the IP data packet temporarily lose their effect. The Mobile IP home agent then tunnels those encapsulated data packet to an agent (Mobile IP foreign agent) on the foreign network to which the mobile node is currently attached. The Mobile IP foreign agent decomposes the capsule and sends the packet to the mobile node, which is currently local to the foreign agent.
[0019] Although the Mobile IP technique is reasonably capable of handling the mobility of user terminals between networks, the Mobile IP technique does increase overhead in the networks, since each data packet must be routed to the home network, encapsulated, and then rerouted to the foreign network. Also, the problems solved by Mobile IP can be viewed as those associated with a macro case of mobility in which nodes (user terminals) are mobile between core networks. Mobile IP is unsuitable for handling a micro case of mobility in which user terminals are mobile between wired access points in a single core network.
[0020] One solution for managing mobility within a circuit-switched cellular network has been proposed and is referred to as Cellular IP. A description of Cellular IP is set forth in a publication by Andras G. Valko entitled “Cellular IP: A New Approach to Internet Host Mobility”, ACM Computer Communication Review, January 1999, the entire content of which is incorporated herein by reference. Although this solution is somewhat suitable for handling mobility in circuit-switched cellular networks, the technique is specific to the circuit-switched infrastructure of the network.
[0021] As can further be appreciated by one skilled in the art, while Mobile IP is suitable for handling cases of user terminal mobility between networks, Mobile IP is deficient in handling problems with packet routing that may occur within a packet-switched core network when a mobile node moves and is handed off from one base station to another. A communications network employing a packet-switched core network is described, for example, in U.S. patent application Ser. No. 09/897,790 entitled “Ad Hoc Peer-to-Peer Mobile Radio Access System Interfaced to the PSTN and Cellular Networks”, filed on Jun. 29, 2001, the entire content of which is incorporated herein by reference. An example of a wireless local area network (LAN) having mobility is set forth in IEEE Standard 802.11, Aug. 20, 1999, the entire content of which is incorporated herein by reference. Specifically, Mobile IP is incapable of effectively operating under the additional constraints imposed by a packet-switched core network having wired access point nodes that are typically connected using bandwidth-constrained leased lines and which cannot tolerate the additional overhead of twice-routed Mobile IP packets. Furthermore, the low-cost access point nodes also typically cannot tolerate the processor-intensive decomposition of encapsulated packets that is performed during Mobile IP.
[0022] In addition to the above deficiencies, other problems involving the manner in which handoff is performed can arise. As explained above, when a user terminal is handed off from one access point to another, the wired network must dynamically reconfigure itself to route packets through the new attachment point. It is often difficult for the wired network to reconfigure itself without the loss of packets sent to the user terminal, because the wired network reconfiguration is not instantaneous. Accordingly, during the reconfiguration period, packets can be sent via both the old and new attachment points. Hence, in existing wireless data networks, one set of these packets will typically be lost.
[0023] Furthermore, as the speed of mobility increases, the frequency in which handoff occurs also increases. With this increase in occurrence of handoff, any loss of packets during handoff becomes more noticeable to the user because it occurs more often. Thus, minimizing packet loss during handoff becomes more important as the speed of mobility increases.
[0024] Accordingly, a need exists for a system and method capable of effectively and efficiently handling mobility of wireless user terminals between access point nodes of a packet-switched network with minimal overhead and packet loss.
Summary of the Invention
[0025] An object of the present invention is to provide a system and method capable of effectively and efficiently handling mobility of wireless user terminals between access point nodes of a communications network, in particular, a packet-switched network, with minimal overhead and packet loss.
[0026] Another object of the present invention is to provide a system and method employing ad-hoc routing techniques for handing off a wireless user terminal between access point nodes of a packet-switched communications network to enable the network to maintain multiple paths via which data packets are provided to the user terminal during handoff to substantially eliminate packet loss during handoff.
[0027] These and other objects are substantially achieved by providing a communications network adapted for use with mobile wireless user terminals, and a method for controlling the network to perform handoff of the user terminals between access points on the network. The network comprises a packet-switched core network, and a plurality of access points coupled to the core network. Each access point is adapted to provide any user terminal with communications access to the core network when the user terminal becomes affiliated with the access point, and includes an address resolution cache which is adapted to store information representative of affiliation between the user terminals and the access points. Each access point can also provide communications access to any user terminal operating in an ad-hoc network.
[0028] When the user terminal changes its affiliation from a first access point to a second access point, a node on the core network other than the first and second access points, such as another access point, a media server, a DNS server, or an IP gateway router, is adapted to continue to send data packets intended for receipt by the user terminal to the first access point until having updated its respective address resolution cache based on a message indicating that the user terminal has changed its affiliation from the first access point to the second access point. The first access point is adapted to continue to send the data packets received from the other node to the user terminal via the wireless connection without sending the data packets to the second access point. Also, an additional node other than the first and second access points and the other node is adapted to send data packets intended for receipt by the user terminal to the second access point after having updated its respective address resolution cache based on the message while the other node continues to send data packets intended for the user terminal to the first access point which continues to send the data packets received from the other node to the user terminal without sending the data packets to the second access point. Furthermore, the second access point is adapted to issue said message over said core network as an address resolution request, such as an address resolution protocol (ARP) request, for an address, such as an IP protocol address, of the user terminal which has changed its affiliation thereto.
Brief Description of the Drawings
[0029] These and other objects, advantages and novel features of the invention will be more readily appreciated from the following detailed description when read in conjunction with the accompanying drawings, in which:
[0030] FIG. 1 is a block diagram of an example of a wireless communications network employing a system and method for handling user terminal mobility within the network according to an embodiment of the present invention;
[0031] FIG. 2 is a conceptual block diagram illustrating affiliation of a mobile user terminal with an access point of the network shown in FIG. 1 ;
[0032] FIG. 3 is a flowchart illustrating an example of operations performed by the network shown in FIG. 1 when a mobile user terminal affiliates with an access point as shown in FIGS. 1 and 2 ;
[0033] FIG. 4 is a block diagram of the network shown in FIG. 1 in which a mobile user terminal changes its affiliation from one access point to another;
[0034] FIG. 5 is a conceptual block diagram illustrating the manner in which a user terminal changes its affiliation with an access point of the network as shown in FIG. 4 ;
[0035] FIG. 6 is a flowchart illustrating an example of operations performed by the network as shown in FIGS. 1 and 4 when the mobile user terminal changes its access point affiliation as shown in FIGS. 4 and 5 ;
[0036] FIG. 7 is a conceptual block diagram illustrating an example of the manner in which the access point to which the user terminal is affiliating communicates this affiliation to the network;
[0037] FIG. 8 is a conceptual block diagram illustrating an example of the manner in which packets are routed during handoff and an exemplary manner in which the access points involved in the handoff negotiate with each other;
[0038] FIG. 9 is a conceptual block diagram illustrating an example of the manner in which routers in the network operate to forward packets to the reaffiliated user while they are processing the reaffiliation communication from the access point with which the user terminal has become affiliated;
[0039] FIG. 10 is a conceptual block diagram illustrating the manner in which the access point from which the user terminal is changing its affiliation communicates this change to the network; and
[0040] FIG. 11 is a conceptual block diagram illustrating an example of the manner in which routers forward packets to the access point with which the user terminal has become affiliated after they have processed the reaffiliation communication.
Detailed Description of the Preferred Embodiments
[0041] FIG. 1 is a block diagram illustrating an example of a wireless communications network 100 employing a system and method for handling user terminal mobility within the network according to an embodiment of the present invention. As shown, network 100, which can be referred to as a “core network”, includes a core local access network (LAN) 102 which provides the wired infrastructure for the network 100. A plurality of intelligent access points (IAP) 104, 106 and 108 are coupled to and communicate with the core LAN 102. As illustrated in this example, IAP 104 is directly coupled to the core LAN 102, while IAP 106 is coupled to core LAN 102 via backhaul interfaces 110 and 112 and a T1 connection, and IAP 108 is coupled to core LAN 102 via backhaul interfaces 114 and 116 and a T1 connection. However, any suitable backhaul technology, such as T3, fiber and microwave, can be used. Hence, the IAPs 104, 106 and 108 need not be fixed, but rather, can be configured to move and can communicate with the core LAN 102 via a wireless backhaul, such as a microwave backhaul.
[0042] Each IAP 104, 106 and 108 is an infrastructure device containing at least one transceiver and at least one embedded processor. In this example, each IAP 104, 106 and 108 further includes a 10/100 Base-T Ethernet connection. However, the IAPs 104, 106 and 108 can include any type of high-speed connection suitable for coupling to the core LAN 102. An IAP 104, 106 and 108 is configured to remain in a fixed location, such as on a building rooftop or in a building ceiling, and is provided with a permanent source of power, such as alternating current or any other suitable power source.
[0043] As described in more detail below, an IAP 104, 106 and 108 operates to provide access for subscriber devices, such as mobile user terminals 118, to wired services provided by the network 100. Each IAP 104, 106 and 108 also provides a respective fixed and known position and location reference, relay and wireless routing for user terminals 118 within its area of coverage, and the principle network management interface with transceivers in wireless routers and subscriber devices, such as user terminals 118. Each wired IAP 104, 106 and 108 can be referred to generally as a “fixed node” on the network 100, while the mobile user terminal 118 can be referred to as a “mobile node”. The wired IAP 104, 106 and 108 can also function as access points to the network 100 for user terminals 118 forming an ad-hoc network as described, for example, in U.S. patent application Ser. No. 09/897,790 reference above, and as in U.S. Pat. No. 5,943,322 to Mayor, the entire contents of each being incorporated by reference herein.
[0044] The network 100 further may include a media server 120 for delivering types of media such as video and multimedia data to the core LAN 102, and a domain name server (DNS) 122 for translating Internet domain names into Internet Protocol (IP) addresses in a manner as known in the art. The network 100 may also include a PSTN gateway 124 which provides data access between the network 100 and the PSTN 126, and an IP gateway router 128 which provides data access between the network 100 and the Internet 130.
[0045] Further details of the network 100 and its operation will now be described. For purposes of this discussion, the terms “IAP” and “node” or “fixed node” will be used interchangeably, as well as the terms “user terminal” and “mobile node”. The wired IAPs 104, 106 and 108 on the core LAN 102 are all fully connected to a single virtual segment. As can be appreciated by one skilled in the art, all IAPs 104, 106 and 108 (fixed nodes) on the virtual segment are directly accessible from any other node at the logical link layer. IP routing is not used to reach any other node on the virtual segment. The IP subnet for this virtual segment is large enough to encompass all of the IAPs 104, 106 and 108, and all mobile nodes 118 in a single broadcast domain. The virtual segment may include media access control layer (MAC-layer) bridges and switches (not shown) between the IAPs 104, 106 and 108, as needed, to filter unicast frames from using bandwidth on non-required links.
[0046] The wired IAPs 104, 106 and 108 will, by definition, have two network interfaces, one of which is connected to the network via a wire-line link, and the other being a wireless transceiver. Both of these interfaces will have IP addresses from the core network's IP subnet. An IAP 104, 106 and 108 must then retain an IP routing table indicating that the IP of the wireless transceiver interface is reachable on that interface, while all other IP addresses on that subnet are reachable directly on the wired interface. IP's outside the core network's subnet are reachable via the core network's directly accessible IP gateway router 128.
[0047] The process by which a mobile node affiliates with an IAP will now be described with reference to FIGS. 1–3 . As a mobile node (user terminal) 118 affiliates to a wired IAP 104, the wired IAP 104 will add that mobile node's IP address to its routing table, indicating that this mobile node is directly accessible via the wireless transceiver. This overrides the default subnet-wide entry only for this particular mobile node. It is noted that the mobile node 118 can affiliate with IAP 104 via a direct communication link, or via other mobile nodes in the ad-hoc network already affiliated with IAP 104. As shown in FIGS. 1 and 2 and in step 1000 in FIG. 3 , mobile node 118 initially affiliates to IAP 104, which is identified as IAP1 in FIG. 2 . Accordingly, in step 1010, IAP 104 adds the IP address of mobile node 118 to its own routing table, indicating that this mobile node 118 is directly accessible via the wireless transceiver of IAP 104. Upon doing so, wired IAP 104 must begin acting as the mobile node's proxy on the core network 100 in step 1020. This implies that IAP 104 will answer to address resolution requests, such as address resolution protocol (ARP) requests, on the core network 100 for the mobile node's IP address as if it were the mobile node 118. Other nodes on the core network 100, such as IAPs 106 and 108, as well as media server 120 (router R1 in FIG. 2 ), DNS server 122 (router R2 in FIG. 2 ) and IP gateway router 124 (not shown in FIG. 2 ), will then associate the IP address of the mobile node 118 to the MAC address of the wired interface of the wired IAP 104 via their respective ARP caching mechanisms in step 1030.
[0048] Furthermore, as indicated in step 1040, when a packet destined for the mobile node 118 is received by the IAP 104, the IAP 104 must consult its IP routing table and forward the packet on the proper interface, which is the wireless transceiver of the IAP 104, as indicated in step 1050. This allows the wired IAP 104 to be a “point of presence” on the core network 100 to represent the mobile node 118 as a proxy.
[0049] It is also necessary for the network 100 to handle the movement of nodes between wired IAPs as will now be described. As shown in FIGS. 4 and 5 and indicated in step 1100 in FIG. 6 , if a mobile node 118 should affiliate to a new IAP, for example, IAP 106, after having received traffic at an original IAP 104, other nodes on the network (e.g., IAP 108, media server 120, DNS server 122 and IP gateway router 124) would be unaware of the change unless certain measures are taken. Hence, their address resolution protocol (ARP) caches would associate the IP of the mobile node 118 to the MAC address of the original IAP 104, so packets from an uninformed node (e.g., IAP 108, media server 120, DNS server 122 or IP gateway router 124) would never reach the new IAP 106.
[0050] To circumvent this problem, a procedure known as “gratuitous ARP” can be performed in accordance with an embodiment of the present invention. As shown in FIG. 5 and in step 1110 of FIG. 6 , before the “gratuitous ARP” procedure is performed, the nodes on the network 100, such as media server 120 and DNS server 122, continue to send packets intended for mobile node 118 to IAP 104. As indicated in step 1120 and in FIG. 7 , the IAP with which the mobile node 118 has newly become associated (i.e., IAP 106) issues an ARP request on network 100 for the mobile node's own IP address. This forces an update to the ARP caches of other nodes (e.g., IAPs 104 and 108, media server 120, DNS server 122 and IP gateway router 124) on the network 100 to the nodes new point of presence, as indicated in step 1130. Further descriptions of ARP caches and gratuitous ARPs are set forth on page 62 of IETF document RFC 2002 referenced above, as well as on page 20 of IETF document RFC 1009 entitled “Requirements for Internet Gateways”, June 1987, and in IETF document RFC 826 entitled “An Ethernet Address Resolution Protocol”, November 1982, the entire contents of each of these documents are incorporated herein by reference. Also, other types of ARP-like mechanisms can be used to update the address resolution caches of the other nodes (IAPs 104 and 108, media server 120, DNS server 122 and IP gateway router 124), such as those mechanisms described in IETF document RFC 2461 entitled “Neighbor Discovery for IP Version 6 (Ipv6)”, December 1998 and in IETF document RFC 2332 entitled “NBMA Next Hop Resolution Protocol”, April 1998, the entire contents of these documents being incorporated herein by reference.
[0051] Hence, other nodes (IAPS 104 and 108, media server 120, DNS server 122 and IP gateway router 124)) will now associate the IP address of the mobile node 118 to the MAC address of the new IAP 106. However, the prior route for packets (i.e., to mobile node 118 via IAP 104) will be maintained for a configurable period to ensure that packets continue to reach the mobile node 118 while the wired network routing is being updated. This ensures an uninterrupted packet stream is maintained. Furthermore, it is important to note that at no time are packets destined for the mobile node forwarded from IAP 104 to IAP 106 during the reconfiguration.
[0052] As further indicated in step 1140 and as shown in FIG. 8 , the new IAP 106 begins to negotiate with the IAP 104 with which the mobile node 118 was previously affiliated to remove the explicit route for the mobile node 118 from this original IAP's IP routing table. For example, the gratuitous ARP may server as the negotiation, or separate messaging may be used.
[0053] It is further noted that the broadcast of the reconfiguration notification, that is, the gratuitous ARP, can on occasion be unreliable or may not immediately be processed by one or more of the nodes on the network 100. For example, as shown in FIG. 9 , the media server 120 (router R1) has received and processed the gratuitous ARP, and is thus sending packets intended for mobile node 118 to the new IAP 106 with which mobile node 118 has become affiliated. However, the DNS server 122 (router R2) has either not received the gratuitous ARP or has not yet processed the gratuitous ARP. Accordingly, DNS server 122, and all other nodes that have either not received or have not yet processed the gratuitous ARP, will continue to send packets intended for mobile node 118 to the old IAP 104 as indicated in step 1150 in FIG. 6 . Once the DNS server 122 has processed the gratuitous ARP, DNS server 122 will then begin to send packets intended for mobile node 118 to the new IAP 106, as shown in FIG. 11 .
[0054] It is also noted that if the IAP 104 continues to receive packets from one or more network nodes after a configurable period, such as a predetermined duration of time (e.g., a few seconds) after the gratuitous ARP has been issued by IAP 106, it will be determined in step 1160 that a network node or nodes must have missed the broadcast of the gratuitous ARP. To overcome this unreliability, a selective retry mechanism can be performed as indicated in step 1170. For example, the IAP 104 can send a notification to the network node or nodes, as shown in FIG. 10 . This notification can either be a broadcast notification, such as a gratuitous ARP, or can be a unicast message to the network node or nodes that are continuing to send packets intended for mobile node 118 to IAP 104. This retry can be triggered a configurable number of times to complete the wired network reconfiguration. After the configurable time period in step 1160, if IAP 104 receives no packets intended for mobile node 118, it is assumed that all packets on the core network 100 are now being sent by default to the wired interface of IAP 106 from all core network nodes, as indicated in step 1180 and in FIG. 11 . The new IAP 106 then completes its negotiation with the IAP 104 with which the mobile node 118 was previously affiliated to remove the explicit route for the mobile node 118 from this original IAP's IP routing table.
[0055] If the mobile node 118 reaffiliates with another IAP (e.g., IAP 108), the above process shown and described with reference to FIGS. 4–11 is repeated.
[0056] It is further noted that the solution described above provides for virtual presence of mobile nodes 118 on a core network 100 and the fall mobility of those nodes between access points on that network. When combined with Mobile IP techniques as discussed in the Background section above, nodes 118 may transit any IAPs, regardless of whether they are on the home network or a foreign network, only using Mobile IP techniques when transitioning between a home network and a foreign networks.
[0057] Although only a few exemplary embodiments of the present invention have been described in detail above, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of this invention. Accordingly, all such modifications are intended to be included within the scope of this invention as defined in the following claims.
Claims
What is claimed is:
1. A communications network, adapted for use with mobile wireless user terminals, said network comprising:
a packet-switched core network; and
a plurality of access points coupled to said core network, each said access point being adapted to provide any said user terminal with communications access to said core network when said any user terminal becomes affiliated with said access point, and including an address resolution cache which is adapted to store information representative of affiliation between said user terminals and said access points, and when a said user terminal changes its affiliation from a first said access point to a second said access point, an other node on said core network other than said first and second access points is adapted to continue to send data packets intended for receipt by said user terminal to said first access point until having updated its respective address resolution cache based on a message indicating that a said user terminal has changed its affiliation from said first access point to said second access point, and said first access point is adapted to continue to send said data packets received from said other node to said user terminal without sending said data packets to said second access point,
wherein when said user terminal changes its affiliation from a first said access point to a second said access point, an additional node other than said first and second access points and said other node is adapted to send data packets intended for receipt by said user terminal to said second access point after having updated its respective address resolution cache based on said message while said other node continues to send data packets intended for said user terminal to said first access point which continues to send said data packets received from said other node to said user terminal without sending said data packets to said second access point.
2. A communications network as claimed in claim 1, wherein:
said additional node includes a said access point.
3. A communications network as claimed in claim 1, wherein:
said other node includes a said access point.
4. A communications network as claimed in claim 1, wherein:
said second access point is adapted to issue said message over said core network as an address resolution request for an address or said user terminal which has changed its affiliation thereto.
5. A communications network as claimed in claim 4, wherein:
said address resolution request includes an address resolution protocol request.
6. A communications network as claimed in claim 4, wherein:
said address of said user terminal includes an Internet protocol address assigned to said user terminal.
7. A communications network as claimed in claim 1, wherein:
said access point with which a said user terminal is affiliated is adapted to transmit a received data packet to said user terminal via a wireless communications link.
8. A communications network as claimed in claim 1, wherein:.
each said access point includes a wireless transceiver, adapted to transmit and receive data packets to and from a said user terminal affiliated therewith via a wireless communications link.
9. A communications network as claimed in claim 1, wherein:
each said address resolution cache includes an address resolution protocol cache.
10. A communications network as claimed in claim 1, further comprising:
at least one of a media server, DNS server and an IP gateway router, each including a respective an address resolution cache which is adapted to store information representative of affiliation between said user terminals and said access points and is updateable based on said message.
11. A communications network as claimed in claim 10, wherein:
said other node includes said media server, said DNS server or said IP gateway router.
12. A communications network as claimed in claim 10, wherein:
said address resolution cache includes an address resolution protocol cache.
13. A communications network as claimed in claim 1, wherein:
each said access point is adapted to provide any said user terminal with communications access to said core network when said user terminal is participating in an ad-hoc network.
14. A method for performing handoff of mobile wireless user terminals between access points on a packet-switched core network in a communications network, each said access point being adapted to provide any said user terminal with communications access to said core network when said any user terminal becomes affiliated with said access point, and including an address resolution cache which is adapted to store information representative of affiliation between said user terminals and said access points, the method comprising:
when a said user terminal changes its affiliation from a first said access point to a second said access point, controlling an other node on said core network other than said first and second access points to continue to send data packets intended for receipt by said user terminal to said first access point until having updated its respective address resolution cache based on a message indicating that a said user terminal has changed its affiliation from said first access point to said second access point; and
while said other node continues to send said data packets to said first access point, controlling said first access point to continue to send said data packets received from said other node to said user terminal without sending said data packets to said second access point,
wherein when said user terminal changes its affiliation from a first said access point to a second said access point, controlling an additional node other than said first and second access points and said other node to send data packets intended for receipt by said user terminal to said second access point after having updated its respective address resolution cache based on said message while said other node continues to send data packets intended for said user terminal to said first access point which continues to send said data packets received from said other node to said user terminal without sending said data packets to said second access point.
17. A method as claimed in claim 14, further comprising:
controlling said second access point to issue said message over said core network as an address resolution request for an address of said user terminal which has changed its affiliation thereto.
18. A method as claimed in claim 17, wherein:
said address resolution request includes an address resolution protocol request.
19. A method as claimed in claim 17, wherein:
said address of said user terminal includes an Internet protocol address assigned to said user terminal.
20. A method as claimed in claim 14, further comprising:
controlling a said access point with which a said user terminal is affiliated is adapted to transmit a received data packet to said user terminal via a wireless communications link.
21. A method as claimed in claim 14, wherein:
each said address resolution cache includes an address resolution protocol cache.
22. A method as claimed in claim 14, wherein:
said other node includes a media server, a DNS server or an IP gateway router.
23. A method as claimed in claim 14, further comprising:
controlling each said access point to provide any said user terminal with communications access to said core network when said user terminal is participating in an ad-hoc network.
24. A computer-readable medium of instructions for controlling a communications network having access points on a packet-switched core network to perform handoff of mobile wireless user terminals between said access points, each said access point being adapted to provide any said user terminal with communications access to said core network when said any user terminal becomes affiliated with said access point, and including an address resolution cache which is adapted to store information representative of affiliation between said user terminals and said access points, the computer-readable medium of instructions comprising:
a first set of instructions which, when a said user terminal changes its affiliation from a first said access point to a second said access point, is adapted to control an other node on said core network other than said first and second access points to continue to send data packets intended for receipt by said user terminal to said first access point until having updated its respective address resolution cache based on a message indicating that a said user terminal has changed its affiliation from said first access point to said second access point;
a second set of instructions which, while said other node continues to send said data packets to said first access point, is adapted to control said first access point to continue to send said data packers received from said other node to said user terminal without sending said data packets to said second access point, and
a third set of instructions which, when said user terminal changes its affiliation from a first said access point to a second said access point, is adapted to control an additional node other than said first and second access points and said other node to send data packets intended for receipt by said user terminal to said second access point after having updated its respective address resolution cache based on said message while said other node continues to send data packets intended for said user terminal to said first access point which continues to send said data packets received from said other node to said user terminal without sending said data packets to said second access point.
25. A computer-readable medium of instructions as claimed in claim 24, wherein:
said additional node includes a said access point.
26. A computer-readable medium of instructions as claimed in claim 24, wherein:
said other node includes a said access point.
27. A computer-readable medium of instructions as claimed in claim 24, further comprising:
a fourth set of instructions which is adapted to control said second access point to issue said message over said core network as an address resolution request for an address of said user terminal which has changed its affiliation thereto.
28. A computer-readable medium of instructions as claimed in claim 27, wherein:
said address resolution request includes an address resolution protocol request.
29. A computer-readable medium of instructions as claimed in claim 27, wherein:
said address of said user terminal includes an Internet protocol address assigned to said user terminal.
30. A computer-readable medium of instructions as claimed in claim 24, further comprising:
a fifth set of instructions, adapted to controlling a said access point with which a said user terminal is affiliated is adapted to transmit a received data packet to said user terminal via a wireless communications link.
31. A computer-readable medium of instructions as claimed in claim 24, wherein:
each said address resolution cache includes an address resolution protocol cache.
32. A computer-readable medium of instructions as claimed in claim 24, wherein:
said other node includes a media server, a DNS server or an IP gateway router.
33. A computer-readable medium of instructions as claimed in claim 24, further comprising:
a sixth set or instructions, adapted to control each said access point to provide any said user terminal with communications access to said core network when said user terminal is participating in an ad-hoc network.
Patent Citations (115)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4494192(A) | 1985-01-01 | Lew et al. | Applicant |
| US4617656(A) | 1986-10-01 | Kobayashi et al. | Applicant |
| US4736371(A) | 1988-04-01 | Tejima et al. | Applicant |
| US4742357(A) | 1988-05-01 | Rackley | Applicant |
| US4747130(A) | 1988-05-01 | Ho | Applicant |
| US4910521(A) | 1990-03-01 | Mellon | Applicant |
| US5034961(A) | 1991-07-01 | Adams | Applicant |
| US5068916(A) | 1991-11-01 | Harrison et al. | Applicant |
| US5231634(A) | 1993-07-01 | Giles et al. | Applicant |
| US5233604(A) | 1993-08-01 | Ahmadi et al. | Applicant |
| US5241542(A) | 1993-08-01 | Natarajan et al. | Applicant |
| US5317566(A) | 1994-05-01 | Joshi | Applicant |
| US5392450(A) | 1995-02-01 | Nossen | Applicant |
| US5412654(A) | 1995-05-01 | Perkins | Applicant |
| US5424747(A) | 1995-06-01 | Chazelas | Applicant |
| US5502722(A) | 1996-03-01 | Fulghum | Applicant |
| US5517491(A) | 1996-05-01 | Nanni et al. | Applicant |
| US5555425(A) | 1996-09-01 | Zeller et al. | Applicant |
| US5555540(A) | 1996-09-01 | Radke | Applicant |
| US5572528(A) | 1996-11-01 | Shuen | Applicant |
| US5615212(A) | 1997-03-01 | Ruszczyk et al. | Applicant |
| US5618045(A) | 1997-04-01 | Kagan et al. | Applicant |
| US5621732(A) | 1997-04-01 | Osawa | Applicant |
| US5623495(A) | 1997-04-01 | Eng et al. | Applicant |
| US5627976(A) | 1997-05-01 | McFarland et al. | Applicant |
| US5631897(A) | 1997-05-01 | Pacheco et al. | Applicant |
| US5644576(A) | 1997-07-01 | Bauchot et al. | Applicant |
| US5652751(A) | 1997-07-01 | Sharony | Applicant |
| US5680392(A) | 1997-10-01 | Semaan | Applicant |
| US5684794(A) | 1997-11-01 | Lopez et al. | Applicant |
| US5687194(A) | 1997-11-01 | Paneth et al. | Applicant |
| US5696903(A) | 1997-12-01 | Mahany | Applicant |
| US5701294(A) | 1997-12-01 | Ward et al. | Applicant |
| US5706428(A) | 1998-01-01 | Boer et al. | Applicant |
| US5717689(A) | 1998-02-01 | Ayanoglu | Applicant |
| US5745483(A) | 1998-04-01 | Nakagawa et al. | Applicant |
| US5774876(A) | 1998-06-01 | Woolley et al. | Applicant |
| US5781540(A) | 1998-07-01 | Malcolm et al. | Applicant |
| US5787080(A) | 1998-07-01 | Hulyalkar et al. | Applicant |
| US5794154(A) | 1998-08-01 | Bar-On et al. | Applicant |
| US5796732(A) | 1998-08-01 | Mazzola et al. | Applicant |
| US5796741(A) | 1998-08-01 | Saito et al. | Applicant |
| US5805593(A) | 1998-09-01 | Busche | Applicant |
| US5805842(A) | 1998-09-01 | Nagaraj et al. | Applicant |
| US5805977(A) | 1998-09-01 | Hill et al. | Applicant |
| US5809518(A) | 1998-09-01 | Lee | Applicant |
| US5822309(A) | 1998-10-01 | Ayanoglu et al. | Applicant |
| US5844905(A) | 1998-12-01 | McKay et al. | Applicant |
| US5845097(A) | 1998-12-01 | Kang et al. | Applicant |
| US5857084(A) | 1999-01-01 | Klein | Applicant |
| US5870350(A) | 1999-02-01 | Bertin et al. | Applicant |
| US5877724(A) | 1999-03-01 | Davis | Applicant |
| US5881095(A) | 1999-03-01 | Cadd | Applicant |
| US5881372(A) | 1999-03-01 | Kruys | Applicant |
| US5886992(A) | 1999-03-01 | Raatikainen et al. | Applicant |
| US5896561(A) | 1999-04-01 | Schrader et al. | Applicant |
| US5903559(A) | 1999-05-01 | Acharya et al. | Applicant |
| US5909651(A) | 1999-06-01 | Chander et al. | Applicant |
| US5936953(A) | 1999-08-01 | Simmons | Applicant |
| US5943322(A) | 1999-08-01 | Mayor et al. | Applicant |
| US5958018(A) | 1999-09-01 | Eng et al. | Applicant |
| US5987011(A) | 1999-11-01 | Toh | Applicant |
| US5987033(A) | 1999-11-01 | Boer et al. | Applicant |
| US5991279(A) | 1999-11-01 | Haugli et al. | Applicant |
| US6028853(A) | 2000-02-01 | Haartsen | Applicant |
| US6029217(A) | 2000-02-01 | Arimilli et al. | Applicant |
| US6034542(A) | 2000-03-01 | Ridgeway | Applicant |
| US6044062(A) | 2000-03-01 | Brownrigg et al. | Applicant |
| US6047330(A) | 2000-04-01 | Stracke, Jr. | Applicant |
| US6052594(A) | 2000-04-01 | Chuang et al. | Applicant |
| US6052752(A) | 2000-04-01 | Kwon | Applicant |
| US6064626(A) | 2000-05-01 | Stevens | Applicant |
| US6067291(A) | 2000-05-01 | Kamerman et al. | Applicant |
| US6078566(A) | 2000-06-01 | Kikinis | Applicant |
| US6104712(A) | 2000-08-01 | Robert et al. | Applicant |
| US6108738(A) | 2000-08-01 | Chambers et al. | Applicant |
| US6115580(A) | 2000-09-01 | Chuprun et al. | Applicant |
| US6122690(A) | 2000-09-01 | Nannetti et al. | Applicant |
| US6130881(A) | 2000-10-01 | Stiller et al. | Applicant |
| US6132306(A) | 2000-10-01 | Trompower | Applicant |
| US6147975(A) | 2000-11-01 | Bowman-Amuah | Applicant |
| US6163699(A) | 2000-12-01 | Naor et al. | Applicant |
| US6178337(B1) | 2001-01-01 | Spartz et al. | Applicant |
| US6192053(B1) | 2001-02-01 | Angelico et al. | Applicant |
| US6192230(B1) | 2001-02-01 | van Bokhorst et al. | Applicant |
| US6208870(B1) | 2001-03-01 | Lorello et al. | Applicant |
| US6223240(B1) | 2001-04-01 | Odenwald et al. | Applicant |
| US6240294(B1) | 2001-05-01 | Hamilton et al. | Applicant |
| US6246875(B1) | 2001-06-01 | Seazholtz et al. | Applicant |
| US6249516(B1) | 2001-06-01 | Brownrigg et al. | Applicant |
| US6275707(B1) | 2001-08-01 | Reed et al. | Applicant |
| US6285892(B1) | 2001-09-01 | Hulyalkar | Applicant |
| US6304556(B1) | 2001-10-01 | Haas | Applicant |
| US6327300(B1) | 2001-12-01 | Souissi et al. | Applicant |
| US6349091(B1) | 2002-02-01 | Li | Applicant |
| US6349210(B1) | 2002-02-01 | Li | Applicant |
| US6434134(B1) | 2002-08-01 | La Porta et al. | Examiner |
| CA2132180 | 1996-03-01 | Applicant | |
| EP513841(A2) | 1992-11-01 | Applicant | |
| EP513841(A3) | 1992-11-01 | Applicant | |
| EP627827(A2) | 1994-12-01 | Applicant | |
| EP924890(A2) | 1999-06-01 | Applicant | |
| FR2683326 | 1993-07-01 | Applicant | |
| WO9608884 | 1996-03-01 | Applicant | |
| WO9724005 | 1997-07-01 | Applicant | |
| WO9839936 | 1998-09-01 | Applicant | |
| WO9912302 | 1999-03-01 | Applicant | |
| WO34932 | 2000-06-01 | Applicant | |
| WO110154 | 2001-02-01 | Applicant | |
| WO133770 | 2001-05-01 | Applicant | |
| WO135567 | 2001-05-01 | Applicant | |
| WO137481 | 2001-05-01 | Applicant | |
| WO137482 | 2001-05-01 | Applicant | |
| WO137483 | 2001-05-01 | Applicant | |
| WO235253 | 2002-05-01 | Applicant |
Non-Patent Literature (19)
- Wong et al., “Soft Handoffs in CDMA Mobile Systems”, Dec. 1997, IEEE Personal Communications.Applicant
- Wong et al., “A Pattern Recognition System for Handoff Algorithms”, Jul. 2000, IEEE Journal on Selected Areas in Communications, vol. 18, No. 7.Applicant
- Andras G. Valko, “Cellular IP: A New Approach to Internet Host Mobility”, Jan. 1999, ACM Computer Communication Review.Applicant
- Richard North, Dale Bryan and Dennis Baker, “Wireless Networked Radios: Comparison of Military, Commercial, and R&D Protocols”, Feb. 28-Mar. 3, 1999, 2nd Annual UCSD Conference on Wireless Communications, San Diego CA.Applicant
- “OSPF Version 2”, Apr. 1998, Internet RFC/STD/FYI/BCP Archives.Applicant
- Benjamin B. Peterson, Chris Kmiecik, Richard Hartnett, Patrick M. Thompson, Jose Mendoza and Hung Nguyen, “Spread Spectrum Indoor Geolocation”, Aug. 1998, Navigation: Journal of the Institute of Navigation, vol. 45, No. 2, summer 1998.Applicant
- Josh Broch, David A. Maltz, David B. Johnson, Yih-Chun Hu and Jorjeta Jetcheva, “A Performance Comparison of Multi-Hop Wireless Ad Hoc Network Routing Protocols”, Oct. 25-30, 1998, Proceedings of the 4th Annual ACM/IEEE International Conference on Mobile Computing and Networking.Applicant
- C. David Young, “USAP: A Unifying Dynamic Distributed Multichannel TDMA Slot Assignment Protocol”.Applicant
- Chip Elliott and Bob Heile, “Self-Organizing Sef-Healing Wireless Networks”, 2000 IEEE.Applicant
- J.J. Garcia-Luna-Aceves and Asimakis Tzamaloukas, “Reversing the Collision-Avoidance Handshake in Wireless Networks”.Applicant
- J.J. Garcia-Luna-Aceves and Marcelo Spohn, “Transmission-Efficient Routing in Wireless Networks Using Link-State Information”.Applicant
- J.J. Garcia-Luna-Aceves and Ewerton L. Madruga, “The Core-Assisted Mesh Protocol”, Aug. 1999, IEEE Journal on Selected Areas in Communications, vol. 17, No. 8.Applicant
- Ad Kamerman and Guido Aben, “Net Throughput with IEEE 802.11 Wireless LANs”.Applicant
- J.R. McChesney and R.J. Saulitis, “Optimization of an Adaptive Link Control Protocol for Multimedia Packet Radio Networks”.Applicant
- Ram Ramanathan and Regina Rosales-Hain, “Topology Control of Multihop Wireless Networks using Transmit Power Adjustment”.Applicant
- Ram Ramanathan and Martha E. Steenstrup, “Hierarchically-Organized, Multihop Mobile Wireless Networks for Quality-of-Service Support”.Applicant
- Martha E. Steenstrup, “Dynamic Multipoint Virtual Circuits for Multimedia Traffic in Multihop Mobile Wireless Networks”.Applicant
- Zhenyu Tang and J.J. Garcia-Luna-Aceves, “Collision-Avoidance Transmission Scheduling for Ad-Hoc Networks”.Applicant
- George Vardakas and Wendell Kishaba, “QoS Networking With Adaptive Link Control and Tactical Multi-Channel Software Radios”.Applicant