Patent Grant
8422467
1. Field of the Invention
The present invention relates to Mobile IP network technology. More particularly, the present invention relates to enabling mobility for a node that changes its location within a network through the use of control messages that are sent and received by access points.
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 related 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 node 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
As shown in
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's home base IP address (associated with segment 12) has been shifted to the Foreign Agent's IP address (associated with segment 14).
Now, suppose that Mobile Node 6 wishes to send a message to a corresponding node 18 from its new location. An output 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 R1 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.”
It is often desirable to assign a unique IP address to each user or device within a network. Moreover various protocols enable automatic assignment of IP addresses within a particular network. For instance, in accordance with the Dynamic Host Configuration Protocol (DHCP), network administrators may manage a network centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network. More particularly, using the Internet's set of protocols (TCP/IP), each device that is capable of connecting to the Internet needs a unique IP address. When an organization sets up its computer users with a connection to the Internet, an IP address must be assigned to each machine. Without DHCP, the IP address must be entered manually at each computer and, if computers move to another location in another part of the network, a new IP address must be entered. DHCP allows a network administrator to supervise and distribute IP addresses from a central point and automatically sends a new IP address when a computer is plugged into a different location within the network.
DHCP uses the concept of a “lease” or amount of time that a given IP address will be valid for a computer. The lease time can vary depending on how long a user is likely to require the Internet connection at a particular location. DHCP is particularly useful in education and other environments where users change frequently. Using very short leases, DHCP can dynamically reconfigure networks in which there are more computers than there are available IP addresses. Thus, DHCP supports static addresses for computers containing Web servers that need a permanent IP address.
Although DHCP functions in a static environment, the assignment of a new IP address each time a computer changes its location within a network is far from ideal within a mobile environment. More particularly, when a mobile node roams to a new location within a network, it would be desirable for the node to maintain its home address. However, provisions have not been made for a node that wishes to maintain a single IP address when it changes its location within a network using DHCP. Moreover, a node that is not mobile enabled cannot currently change its location within a network using DHCP and still maintain its assigned IP address.
In view of the above, it would be desirable to provide Internet services via a wireless link for mobile users who attach to a network via a connection such as a DHCP connection. Moreover, it would be beneficial if such capabilities could be provided even where the node does not support Mobile IP.
The present invention provides proxy mobile IP support for a node that changes its location within a network. This is accomplished, in part, through the communication between access points within the network. An Access Point (AP) is the center point in an all-wireless network or serves as a connection point between a wired and a wireless network. Multiple APs can be placed throughout a facility to give users with WLAN adapters the ability to roam freely throughout an extended area while maintaining uninterrupted access to all network resources. Through the use of such communication, access point information associated with multiple APs may be maintained, enabling registration and de-registration of the node with a Home Agent to be initiated by an Access Point. Once registered with the Home Agent, packets may be forwarded by the Home Agent to the Foreign Agent. Moreover, the access point may also redirect packets sent by the node to the Foreign Agent, enabling the redirected packets to be sent to the appropriate destination by the Foreign Agent.
In accordance with one aspect of the invention, methods and apparatus for supporting a node that does not support Mobile IP are disclosed. An authoritative access point (AAP) maintains network subnet information as well as access point information for all functioning access points (APs) (i.e., active APs) and sends updates to the functioning APs regarding additions or other modifications to the continually changing access point information. For instance, when an AP goes offline, the access point information for that AP will be removed from the set of access point information, and notification of this removal is sent to other APs so that the local copy of the AP information may be similarly updated. As another example, when an AP comes online, it will send its AP information to the AAP. The AAP will store the AP information and provide this new AP information to other “active” APs. The AP information preferably includes an AP subnetwork (subnet) and a gateway.
In accordance with another aspect of the invention, methods and apparatus for sending a mobile IP registration request on behalf of a node that does not support Mobile IP are disclosed. When an AP receives a data packet, the AP may compare the data packet (e.g., source address) with the AP information for one or more APs to determine whether to send a registration request on behalf of the node. More particularly, the AP determines from the source address whether the node is located on a subnet identical to a subnet of the AP. If the node is located on the subnet of the AP, no Mobile IP service is required on behalf of the node. However, when it is determined from the source address that the node is not located on the subnet identical to the subnet of the Access Point, the AP composes and sends a mobile IP registration request on behalf of the node. For instance, the mobile IP registration request may be composed using the gateway associated with the “home” AP (e.g., having a matching subnet) as the node's Home Agent.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be obvious, however, to one skilled in the art, that the present invention may be practiced without some or all of these specific details. In other instances, well known process steps have not been described in detail in order not to unnecessarily obscure the present invention.
An invention is described herein that enables a node (e.g., a node that does not implement the Mobile IP protocol) to roam to various Foreign Agents within a network such as a DHCP supported network. This is accomplished, in part, through the use of control messages sent between the access points within the network. For purposes of the following discussion, the term “mobile node” will be used to refer to a mobile node implementing the Mobile IP protocol while the term “node” will be used to refer to a node that does not implement the Mobile IP protocol.
In a wireless network, Access Points 210 and 212 are coupled to the Foreign Agents 202 and 204. By way of example, in a wireless network, the Access Points 210 and 212 may have an antenna and receiver for receiving packets. As yet another example, the Access Points 210 and 212 may designate connection points in a non-wireless network. Typically, a mobile node implementing Mobile IP registers and de-registers with its Home Agent through the registration process. However, according to the present invention, registration is initiated by the Access Point on behalf of the Mobile IP node. Similarly, de-registration may be initiated by the Access Point on behalf of the roaming node. For instance, node 206 that has roamed to the first Foreign Agent 202 is registered with the node's Home Agent 200 when the first Access Point 206 composes and sends a registration request packet via the first Foreign Agent 202. Thus, the first Foreign Agent's visitor table and the Home Agent's mobility binding table are updated to indicate that the node has roamed to the first Foreign Agent 202. When the node 206 roams to the second Foreign Agent 204, the node 206 is de-registered (e.g., by one of the Access Points 210, 212, either of the Foreign Agents 202, 204 or the Home Agent 200). In other words, the first Foreign Agent 202 updates its visitor table to reflect the movement of the node 206. Similarly, the Home Agent's mobility binding table is updated to reflect the movement of the node 206 to the second Foreign Agent 204. Thus, the appropriate entry in the first Foreign Agent's visitor table and the Home Agent's mobility binding table may be deleted. A new entry is then entered in the Home Agent's mobility binding table and the second Foreign Agent's visitor table upon completion of registration of the mobile node with the Home Agent. Alternatively, the visitor table may be maintained and updated by the Access Point.
Three exemplary methods of detecting a node are listed here. First, a node may be detected upon receipt of an Address Resolution Protocol (ARP) request. More particularly, in order to send a packet to a destination IP address, a node must obtain the MAC address or “link-layer address” associated with the destination IP address. A node typically obtains a MAC address associated with an intended destination IP address by sending an ARP request to the Foreign Agent via the Access Point. Second, a node may attempt to send an actual data packet via the Foreign Agent. Thus, in this instance, the receipt of the data packet by the Access Point triggers the sending of a control packet (i.e., registration request packet) by the Access Point. Third, an access point control packet may be received. For instance, when a device communicates with an access point, the access point composes and sends a registration request packet via the Foreign Agent. This third method is preferred since continuously sending ARP requests and listening to data packets provides an unnecessary amount of traffic in a network having a limited bandwidth.
In accordance with one embodiment of the invention, access point control messages are used by an authoritative access point (AAP) and one or more access points to communicate information about the respective access points. More particularly, access point information may be transmitted among the access points so that each access point may store a local copy of the access point information. This access point information may be used to determine whether a node has roamed to a particular access point, and therefore requires proxy Mobile IP service.
The present invention enables an Access Point (AP) that supports Mobile IP to perform proxy registration on behalf of a node that does not support Mobile IP. This is accomplished by maintaining AP information for active APs. In accordance with one embodiment, multiple APs maintain identical local copies of a subnet mapping table that stores AP information for the multiple APs. More specifically, when an AP comes online, it is considered “active” and provides its AP information to other active APs. This exchange and distribution of AP information is preferably performed via an authoritative AP (AA) responsible for receiving AP information from a newly active AP and distributing that received AP information to other active APs. Similarly, the authoritative AP also provides the newly active AP with AP information from the other active APs. Thus, the AAP and all other APs maintain identical subnet mapping tables. From the AP information in the subnet mapping table, an AP may ascertain when Mobile IP service is required, thereby enabling the AP to compose and send a Mobile IP registration request on behalf of the node.
In addition to updating its own subnet mapping table, the AAP sends the access point information for the newly active AP to all other active APs identified in the active AP list, as well as any additional AP information associated with other active APs from the subnet mapping table to the newly active AP at block 308. As described above, the active AP list may identify one or more active access points. Upon receipt of the access point information, the active APs store the received AP information at block 310. In addition, it is important to note that at block 312 the newly active AP also stores its own AP information (e.g., in its subnet mapping table) as well as that received from the AAP at block 308. For instance, the AP information may be stored in a subnet mapping table such as that described below with reference to
Once an active AP has configured its subnet mapping table, the table may become corrupted or otherwise need to be refreshed with the subnet mapping table maintained by the AAP.
Rather than adding AP information to a subnet mapping table or obtaining information from a subnet mapping table, it may be desirable to remove AP information from a subnet mapping table.
Once an AP is configured with AP information for one or more APs, such as that stored in a subnet mapping table described below with reference to
The AP ascertains the access point subnet identical to that of the node at block 506 by identifying the matching subnet entry at block 506. The entry in the subnet mapping table is then obtained at block 508 to determine the node subnet and gateway. The AP then determines whether the access point subnet identical to that of the node is different from the subnet of the Access Point at block 510. When the AP determines from the source address that the node is located on the subnet identical to the subnet of the Access Point, no Mobile IP service is required on behalf of the node as shown at block 512. When the AP determines from the source address that the node is not located on the subnet of the Access Point, proxy Mobile IP service is required as shown at block 514. The AP may then obtain the access point information. Once the AP has obtained the access point information, the AP acts on behalf of the node and composes and sends a mobile IP registration request ion behalf of the node as shown at block 516. In accordance with one embodiment, the registration request is composed such that it specifies the gateway as the node's Home Agent.
As described above, each AP (and AAP) preferably maintains its own local subnet mapping table.
More specifically,
In order to obtain access point information associated with one or more access points (e.g., a subnet mapping table or portion thereof) as described above with reference to
An acknowledgement packet (ACK) may be sent in response to various control commands such as the ADD or REMOVE packets as described above with reference to
Similarly, an ERROR packet may be sent as described above with reference to
As described above, when a node that is roaming wishes to send a message to a corresponding node from its new location, a message from the roaming node is packetized and forwarded through the Foreign Agent it is visiting over the internet and to the corresponding node. Thus, when the node roams, it is desirable to redirect packets sent by the node to the appropriate Foreign Agent. In accordance with one embodiment, the access point is responsible for such redirection of packets. Since the access point redirects packets sent by the node through the appropriate Foreign Agent, it is desirable to notify the access point when registration is completed successfully.
Other Embodiments
Generally, the techniques of the present invention may be implemented on software and/or hardware. For example, they can be implemented in an operating system kernel, in a separate user process, in a library package bound into network applications, on a specially constructed machine, or on a network interface card. In a specific embodiment of this invention, the technique of the present invention is implemented in software such as an operating system or in an application running on an operating system.
A software or software/hardware hybrid implementation of the techniques of this invention may be implemented on a general-purpose programmable machine selectively activated or reconfigured by a computer program stored in memory. Such a programmable machine may be a network device designed to handle network traffic, such as, for example, a router or a switch. Such network devices may have multiple network interfaces including frame relay and ISDN interfaces, for example. Specific examples of such network devices include routers and switches. For example, the Access Points of this invention may be implemented in specially configured routers or servers, as well as Cisco Aironet 350 Series Access Points, available from Cisco Systems, Inc. of San Jose, Calif. A general architecture for some of these machines will appear from the description given below. In an alternative embodiment, the techniques of this invention may be implemented on a general-purpose network host machine such as a personal computer or workstation. Further, the invention may be at least partially implemented on a card (e.g., an interface card) for a network device or a general-purpose computing device.
Referring now to
CPU 1562 may include one or more processors 1563 such as a processor from the Motorola family of microprocessors or the MIPS family of microprocessors. In an alternative embodiment, processor 1563 is specially designed hardware for controlling the operations of network device 1560. In a specific embodiment, a memory 1561 (such as non-volatile RAM and/or ROM) also forms part of CPU 1562. However, there are many different ways in which memory could be coupled to the system. Memory block 1561 may be used for a variety of purposes such as, for example, caching and/or storing data, programming instructions, etc.
The interfaces 1568 are typically provided as interface cards (sometimes referred to as “line cards”). Generally, they control the sending and receiving of data packets over the network and sometimes support other peripherals used with the network device 1560. Among the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various very high-speed interfaces may be provided such as fast Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces, ASI interfaces, DHEI interfaces and the like. Generally, these interfaces may include ports appropriate for communication with the appropriate media. In some cases, they may also include an independent processor and, in some instances, volatile RAM. The independent processors may control such communications intensive tasks as packet switching, media control and management. By providing separate processors for the communications intensive tasks, these interfaces allow the master microprocessor 1562 to efficiently perform routing computations, network diagnostics, security functions, etc.
Although not shown, various removable antennas may be used for further increase range and reliability of the access points. In addition, radio transmit power e.g., 1, 5, 20, 30, 50, and 100 mW) on the Cisco Aironet 350 Series is configurable to meet coverage requirements and minimize interference. In addition, a Cisco Aironet AP can be configured as a redundant hot standby to another AP in the same coverage area. The hot-standby AP continually monitors the primary AP on the same channel, and assumes its role in the rare case of a failure of the primary AP.
Although the system shown in
Regardless of network device's configuration, it may employ one or more memories or memory modules (such as, for example, memory block 1565) configured to store data, program instructions for the general-purpose network operations and/or other information relating to the functionality of the techniques described herein. The program instructions may control the operation of an operating system and/or one or more applications, for example.
Because such information and program instructions may be employed to implement the systems/methods described herein, the present invention relates to machine readable media that include program instructions, state information, etc. for performing various operations described herein. Examples of machine-readable media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM) and random access memory (RAM). The invention may also be embodied in a carrier wave travelling over an appropriate medium such as airwaves, optical lines, electric lines, etc. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter.
Although illustrative embodiments and applications of this invention are shown and described herein, many variations and modifications are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those of ordinary skill in the art after perusal of this application. For instance, although the specification has described access points, other entities used to tunnel packets to mobile nodes on remote network segments can be used as well. For example, routers, bridges or other less intelligent packet switches may also employ the standby protocol of this invention. Moreover, although the present invention is useful for nodes that do not support Mobile IP, the invention may also be applicable for nodes that support Mobile IP. Moreover, the present invention may be applicable in a network supported by various protocols such as DHCP. In addition, each AP need not maintain local copies of the subnet mapping table. Rather, a centralized subnet mapping table may be maintained (e.g., by the AAP). In addition, control packets such as the ADD, GET, and REMOVE packets may be sent to multiple APs rather than solely to the AAP.
Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
This application is a divisional application of patent application Ser. No. 10/080,995, entitled, “Methods and Apparatus for Supporting Proxy Mobile IP Registration in a Wireless Local Area Network,” by Wang et al, filed on Feb. 20, 2002 now U.S. Pat. No. 7,471,661, which is incorporated herein by reference for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4692918 | Elliott et al. | Sep 1987 | A |
| 5016244 | Massey et al. | May 1991 | A |
| 5018133 | Tsukakoshi et al. | May 1991 | A |
| 5218600 | Schenkyr et al. | Jun 1993 | A |
| 5276680 | Messenger | Jan 1994 | A |
| 5371852 | Attanasio et al. | Dec 1994 | A |
| 5473599 | Li et al. | Dec 1995 | A |
| 5490139 | Baker et al. | Feb 1996 | A |
| 5570366 | Baker et al. | Oct 1996 | A |
| 5572528 | Shuen | Nov 1996 | A |
| 5619552 | Karppanen et al. | Apr 1997 | A |
| 5729537 | Billstrom | Mar 1998 | A |
| 5751799 | Mori | May 1998 | A |
| 5805702 | Curry et al. | Sep 1998 | A |
| 5825759 | Liu | Oct 1998 | A |
| 5862345 | Okanoue et al. | Jan 1999 | A |
| 5978672 | Hartmaier et al. | Nov 1999 | A |
| 6016428 | Diachina et al. | Jan 2000 | A |
| 6055236 | Nessett et al. | Apr 2000 | A |
| 6061650 | Malkin et al. | May 2000 | A |
| 6075783 | Voit | Jun 2000 | A |
| 6078575 | Dommety et al. | Jun 2000 | A |
| 6079020 | Liu | Jun 2000 | A |
| 6081507 | Chao et al. | Jun 2000 | A |
| 6122268 | Okanoue et al. | Sep 2000 | A |
| 6131095 | Low et al. | Oct 2000 | A |
| 6137791 | Frid et al. | Oct 2000 | A |
| 6144671 | Perinpanathan et al. | Nov 2000 | A |
| 6154839 | Arrow et al. | Nov 2000 | A |
| 6163843 | Inoue et al. | Dec 2000 | A |
| 6167513 | Inoue et al. | Dec 2000 | A |
| 6172986 | Watanuki et al. | Jan 2001 | B1 |
| 6173399 | Gilbrech | Jan 2001 | B1 |
| 6175917 | Arrow et al. | Jan 2001 | B1 |
| 6195705 | Leung | Feb 2001 | B1 |
| 6226748 | Bots et al. | May 2001 | B1 |
| 6226751 | Arrow et al. | May 2001 | B1 |
| 6230012 | Willkie et al. | May 2001 | B1 |
| 6240089 | Okanoue et al. | May 2001 | B1 |
| 6256300 | Ahmed et al. | Jul 2001 | B1 |
| 6272129 | Dynarski et al. | Aug 2001 | B1 |
| 6308267 | Gremmelmaier | Oct 2001 | B1 |
| 6339830 | See et al. | Jan 2002 | B1 |
| 6377982 | Rai et al. | Apr 2002 | B1 |
| 6393482 | Rai et al. | May 2002 | B1 |
| 6396828 | Liu | May 2002 | B1 |
| 6400722 | Chuah et al. | Jun 2002 | B1 |
| 6445922 | Hiller et al. | Sep 2002 | B1 |
| 6452920 | Comstock | Sep 2002 | B1 |
| 6453159 | Lewis | Sep 2002 | B1 |
| 6466964 | Leung et al. | Oct 2002 | B1 |
| 6473413 | Chiou et al. | Oct 2002 | B1 |
| 6487406 | Chang et al. | Nov 2002 | B1 |
| 6496491 | Chuah et al. | Dec 2002 | B2 |
| 6496855 | Hunt et al. | Dec 2002 | B1 |
| 6501746 | Leung | Dec 2002 | B1 |
| 6510144 | Dommety et al. | Jan 2003 | B1 |
| 6515974 | Inoue et al. | Feb 2003 | B1 |
| 6522880 | Verma et al. | Feb 2003 | B1 |
| 6535493 | Lee et al. | Mar 2003 | B1 |
| 6571289 | Montenegro | May 2003 | B1 |
| 6577643 | Rai et al. | Jun 2003 | B1 |
| 6578085 | Khalil et al. | Jun 2003 | B1 |
| 6587882 | Inoue et al. | Jul 2003 | B1 |
| 6597882 | Tanaka | Jul 2003 | B1 |
| 6625135 | Johnson et al. | Sep 2003 | B1 |
| 6651105 | Bhagwat et al. | Nov 2003 | B1 |
| 6657981 | Lee et al. | Dec 2003 | B1 |
| 6665537 | Lioy | Dec 2003 | B1 |
| 6671735 | Bender | Dec 2003 | B1 |
| 6675208 | Rai et al. | Jan 2004 | B1 |
| 6683871 | Lee et al. | Jan 2004 | B1 |
| 6684241 | Sandick et al. | Jan 2004 | B1 |
| 6701437 | Hoke et al. | Mar 2004 | B1 |
| 6707809 | Warrier et al. | Mar 2004 | B1 |
| 6731621 | Mizutani et al. | May 2004 | B1 |
| 6742036 | Das et al. | May 2004 | B1 |
| 6760444 | Leung | Jul 2004 | B1 |
| 6763007 | La Porta et al. | Jul 2004 | B1 |
| 6795857 | Leung et al. | Sep 2004 | B1 |
| 6798763 | Kimura et al. | Sep 2004 | B1 |
| 6810259 | Zhang | Oct 2004 | B1 |
| 6947401 | El-Malki et al. | Sep 2005 | B2 |
| 6973068 | Inoue et al. | Dec 2005 | B2 |
| 6982967 | Leung | Jan 2006 | B1 |
| 6992994 | Das et al. | Jan 2006 | B2 |
| 6992995 | Agrawal et al. | Jan 2006 | B2 |
| 6996084 | Troxel et al. | Feb 2006 | B2 |
| 7068640 | Kakemizu et al. | Jun 2006 | B2 |
| 7079499 | Akhtar et al. | Jul 2006 | B1 |
| 7079520 | Feige et al. | Jul 2006 | B2 |
| 7080151 | Borella et al. | Jul 2006 | B1 |
| 7096273 | Meier | Aug 2006 | B1 |
| 7130629 | Leung et al. | Oct 2006 | B1 |
| 7134012 | Doyle et al. | Nov 2006 | B2 |
| 7139833 | Heller | Nov 2006 | B2 |
| 7152238 | Leung et al. | Dec 2006 | B1 |
| 7161913 | Jung | Jan 2007 | B2 |
| 7170892 | Major | Jan 2007 | B2 |
| 7216159 | Hirose et al. | May 2007 | B2 |
| 7236469 | Yokota et al. | Jun 2007 | B2 |
| 7260638 | Crosbie | Aug 2007 | B2 |
| 7289631 | Ishidoshiro | Oct 2007 | B2 |
| 7339903 | O'Neil | Mar 2008 | B2 |
| 7339928 | Choyi et al. | Mar 2008 | B2 |
| 7362742 | Siddiqi et al. | Apr 2008 | B1 |
| 7428226 | Adrangi et al. | Sep 2008 | B2 |
| 7447188 | Dommety et al. | Nov 2008 | B1 |
| 7457289 | Wang | Nov 2008 | B2 |
| 7471661 | Wang et al. | Dec 2008 | B1 |
| 7505432 | Leung et al. | Mar 2009 | B2 |
| 20010005369 | Kloth | Jun 2001 | A1 |
| 20010036184 | Kinoshita et al. | Nov 2001 | A1 |
| 20020021689 | Robbins et al. | Feb 2002 | A1 |
| 20020075866 | Troxel et al. | Jun 2002 | A1 |
| 20020078238 | Troxel et al. | Jun 2002 | A1 |
| 20020080752 | Johansson et al. | Jun 2002 | A1 |
| 20020147837 | Heller | Oct 2002 | A1 |
| 20020188562 | Igarashi et al. | Dec 2002 | A1 |
| 20030002468 | Khalil et al. | Jan 2003 | A1 |
| 20030021275 | Shabeer | Jan 2003 | A1 |
| 20030212794 | Touati et al. | Nov 2003 | A1 |
| 20040001513 | Major et al. | Jan 2004 | A1 |
| 20040024901 | Agrawal et al. | Feb 2004 | A1 |
| 20040081086 | Hippelainen et al. | Apr 2004 | A1 |
| 20040103282 | Meier et al. | May 2004 | A1 |
| 20040109452 | Takihiro et al. | Jun 2004 | A1 |
| 20040114559 | Wang | Jun 2004 | A1 |
| 20040208187 | Mizell et al. | Oct 2004 | A1 |
| 20040213172 | Myers et al. | Oct 2004 | A1 |
| 20040213260 | Leung | Oct 2004 | A1 |
| 20050249210 | Heller | Nov 2005 | A1 |
| 20060007911 | Hankins et al. | Jan 2006 | A1 |
| 20060114856 | Hirata et al. | Jun 2006 | A1 |
| 20060203804 | Whitmore et al. | Sep 2006 | A1 |
| 20090141688 | Leung et al. | Jun 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| 0924913 | Jun 1999 | EP |
| 0978977 | Feb 2000 | EP |
| 1124396 | Aug 2001 | EP |
| Entry |
|---|
| Canadian Office Action mailed Aug. 6, 2010 from related CA Application No. 2,520,501. |
| Chinese Office Action mailed Aug. 12, 2010 from related CN Application No. 200480010365.7. |
| European Office Action mailed Jun. 14, 2010 from related EP Application No. 04750992.2. |
| European Office Action mailed Aug. 19, 2010 from related EP Application No. 04750992.2. |
| C. Perkins, Editor “IP Mobility Support,” RFC 2002, IBM Corporation, Oct. 1996, 56 pgs. |
| Canadian Office Action mailed Jan. 6, 2009 from related CA Application No. 2,520,501, 5 pgs. |
| Chinese Office Action mailed Mar. 27, 2009 from related CN Application No. 200480010365.7, 5 pgs. |
| U.S. Office Action dated Jun. 2, 2006 from related U.S. Appl. No. 10/080,995, 15 pgs. |
| U.S. Office Action dated Nov. 24, 2006 from related U.S. Appl. No. 10/080,995, 10 pgs. |
| U.S. Office Action dated Feb. 9, 2007 from related U.S. Appl. No. 10/080,995,13 pgs. |
| U.S. Office Action dated Jul. 19, 2007 from related U.S. Appl. No. 10/080,995, 9 pgs. |
| U.S. Office Action dated Nov. 8, 2007 from related U.S. Appl. No. 10/080,995, 9 pgs. |
| Notice of Allowance and Allowed Claims dated Apr. 11, 2008 from U.S. Appl. No. 10/080,995, 18 pgs. |
| Release notes for 3Com Corporation, “Conducting a Redundant Route for Network Resiliency,” Mar. 1994, NET Builder Family Bridge/Router pp. 26-29. |
| Uyless Black, “TCP/IP and Related Protocols,” 1992, McGraw-Hill, Inc., pp. 226-249. |
| T. Li et al., RFC 2281 “Cisco Hot Standby Router Protocol (HSRP),” Mar. 1998. |
| Chambless et al., “Home Agent Redundancy Protocol (HARP),” Oct. 27, 1997. |
| Network Working Group, RFC 2002 “IP Mobility Support,” Oct. 1996, 80 pgs. |
| “Mobile IP,” Release 12.0(1)T, pp. 1-55 on or before Jul. 25, 2002. |
| Montenegro, G., “Reverse Tunneling for Mobile IP,” RFC 2344, Sun Microsystems, Inc. pp. 1-19, May 1998. |
| D. Harkins and D. Carrel, “The Internet Key Exchange (IKE),” Cisco Systems, pp. 1-33, Jun. 1998. |
| D. Cong, M. Hamlen, and C. Perkins, “The Definitions of Managed Objects for Ip Mobility Support Using SMIv2,” RFC2006, Motorola and IBM, pp. 1-52, Oct. 1996. |
| J. Moy, RFC 1247 “OSPF Version 2,” Jul. 19, 1991. |
| D. Oran, RFC 1142 “OSI IS-IS Intra-domain Routing Protocol,” Feb. 1990. |
| C. Finseth, “An Access Control Protocol, Sometimes Called TACACS,” RFC 1492, pp. 1-15, Sep. 13, 1992. |
| D. Carrel and Lol Grant, “The TACACS+ Protocol,” Network Working Group, Internet-Draft, Cisco Systems, pp. 1-42, Jan. 1997. |
| C. Rigney, “RADIUS Accounting,” RFC 2139, Livingston, pp. 1-25, Apr. 1997. |
| C. Rigney et al., “Remote Authentication Dial in User Service (RADIUS),” RFC 2138, pp. 1-65 Apr. 1997. |
| Charles Perkins, “Mobile IP Design Principles and Practices”, Addison Wesley, 1998, pp. 50, 55-59, 83, 78. |
| R. Droms, “Dynamic Host Configuration Protocol”, RFC 2131, Mar. 1997, pp. 1-39. |
| Helmy et al., “Efficient Micro-Mobility using Intra-Domain Multicast-Based Mechanisms (M&M)”, ACM SIGCOMM Computer Communications Review, vol. 32, No. 5: Nov. 2002, pp. 61-72, XP-002279254. |
| Calhoun and Perkins, “Mobile IP Network Access Identifier Extension for IPv4”, Jan. 12, 2000. |
| J. Postel, “Simple Mail Transfer Protocol”, STD 10, RFC 821, Aug. 1982. |
| D. Crocker and P. Overrell, “Augmented BNF for Syntax Specifications: ABNF”, RFC 2234, Nov. 1997. |
| Perkins & Hobby, Network Working Group, RFC 1172 “The Point-to-Point Protocol (PPP) Initial Configuration Options”, Jul. 1990. |
| International Search Report mailed May 21, 2004 in related PCT Application No. PCT/US03/38568, 4 pgs. |
| International Search Report mailed Oct. 5, 2004 in related PCT Application No. PCT/US04/013365, 7 pgs. |
| B. Adoba et al., “The Network Access Identifier,” Network Working Group, RFC 2486 Jan. 1999. |
| W. Simpson, Network Working Group, RFC 1994 PPP Challenge Handshake Authentication Protocol (CHAP), Aug. 1996. |
| Lloyd et al., Network Working Group, RFC 1334 “PPP Authentication Protocols”, Oct. 1992. |
| McGregor, Network Working Group, RFC 1332 “The PPP Internet Control Protocol (IPCP),” May 1992. |
| Simpson, ed., Network Working Group, RFC 1661, “The Point-to-Point Protocol (PPP)”, Jul. 1994. |
| U.S. Office Action dated Dec. 15, 2006 from related U.S. Appl. No. 10/321,080, 11 pgs. |
| U.S. Office Action dated Jul. 3, 2007 from related U.S. App. No. 10/321,080, 11 pgs. |
| U.S. Office Action mailed Jan. 25, 2007 from related U.S. Appl. No. 10/354,690, 26 pgs. |
| U.S. Office Action mailed Jul. 3, 2007 from related U.S. Appl. No. 10/354,690, 18 pgs. |
| Mobile Networking Through Mobile IP, Perkins, IEEE 1998. |
| U.S. Office Action dated Apr. 17, 2007 from related U.S. Appl. No. 10/426,106, 9 pgs. |
| U.S. Office Action dated Jun. 15, 2007 from related U.S. Appl. No. 10/426,106, 13 pgs. |
| U.S. Office Action dated Jun. 4, 2007 from related U.S. Appl. No. 10/874,679, 14 pgs. |
| U.S. Office Action dated Nov. 28, 2007 from related U.S. Appl. No. 10/874,679, 16 pgs. |
| Notice of Allowance and Allowed Claims dated Nov. 29, 2007 from U.S. Appl. No. 10/354,690, 16 pgs. |
| U.S. Office Action dated Dec. 12, 2007 from related U.S. Appl. No. 10/321,080, 10 pgs. |
| U.S. Office Action dated Dec. 12, 2007 from related U.S. Appl. No. 10/426,106, 12 pgs. |
| U.S. Office Action dated Apr. 29, 2008 from related U.S. Appl. No. 10/426,106, 15 pgs. |
| Notice of Allowance and Allowed Claims dated Jun. 24, 2008 from related U.S. Appl. No. 10/874,679, 27 pgs. |
| Notice of Allowance and Allowed Claims dated Jul. 14, 2008 from U.S. Appl. No. 10/321,080, 23 pgs. |
| Notice of Allowance and Allowed Claims dated Aug. 21, 2008 from corresponding U.S. Appl. No. 10/080,995, 15 pgs. |
| European Office Action mailed Aug. 20, 2008 from related EP Application No. 04750992.2, 5pgs. |
| Australian Office Action mailed Sep. 26, 2008 from related AU Application No. 2004234700, 2 pgs. |
| Notice of Allowance and Allowed Claims dated Oct. 31, 2008 from U.S. Appl. No. 10/426,106. |
| U.S. Office Action dated Jul. 12, 2011 from related U.S. Appl. No. 12/368,159. |
| Canadian Office Action mailed Jul. 9, 2011 from related CA Application No. 2,520,501. |
| U.S. Notice of Allowance dated Jan. 13, 2012 from related U.S. Appl. No. 12/368,159. |
| International Preliminary Report on Patentability mailed Oct. 28, 2005 issued in PCT Application No. PCT/US2004/013365. |
| U.S. Notice of Allowance dated Mar. 12, 2012 from related U.S. Appl. No. 12/368,159. |
| U.S. Notice of Allowance dated Aug. 13, 2012 from related U.S. Appl. No. 12/368,159. |
| Number | Date | Country | |
|---|---|---|---|
| 20090080399 A1 | Mar 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10080995 | Feb 2002 | US |
| Child | 12323384 | US |
