US20030217180A1 - DHCP based home address management of mobile IP clients - Google Patents

DHCP based home address management of mobile IP clients Download PDF

Info

Publication number
US20030217180A1
US20030217180A1 US10300437 US30043702A US2003217180A1 US 20030217180 A1 US20030217180 A1 US 20030217180A1 US 10300437 US10300437 US 10300437 US 30043702 A US30043702 A US 30043702A US 2003217180 A1 US2003217180 A1 US 2003217180A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
mobile node
dhcp
home agent
home
registration
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US10300437
Other versions
US7461169B2 (en )
Inventor
Madhavi Chandra
Milind Kulkarni
Kent Leung
Alpesh Patel
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Cisco Technology Inc
Original Assignee
Cisco Technology Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04Registration at HLR or HSS [Home Subscriber Server]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2007Address allocation internet protocol [IP] addresses
    • H04L61/2015Address allocation internet protocol [IP] addresses using the dynamic host configuration protocol [DHCP] or variants
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12207Address allocation
    • H04L29/12273Address allocation involving timing and renewal aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2053Address allocation involving timing or renewal aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W60/00Registration, e.g. affiliation to network; De-registration, e.g. terminating affiliation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W8/00Network data management
    • H04W8/26Network addressing or numbering for mobility support
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation, e.g. WAP [Wireless Application Protocol]
    • H04W80/04Network layer protocols, e.g. mobile IP [Internet Protocol]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18Service support; Network management devices

Abstract

Methods and apparatuses for allowing mobile nodes to have access to mobility functions after being attached to their home networks. The invention allows a home agent to authenticate a registration request and validate a DHCP-acquired home address even if no mobile bindings currently exist. Typically, a home agent will not create mobility bindings if a mobile node attaches itself to a home agent network segment. By using either cached information or DHCP resources, the home agent can approve a registration request.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation-in-part of U.S. application Ser. No. 10/241,969, filed Sep. 11, 2002, which claims the benefit of U.S. Provisional Application No. 60/362,251, filed Mar. 5, 2002, both of which are incorporated herein by reference in their entireties and for all purposes. This application is related to Ser. No. 10/150,377, filed May 17, 2002, and Ser. No. 10/187,084, filed Jun. 28, 2002, both of which are incorporated herein by reference in their entireties and for all purposes, and both of which claim benefit of U.S. Provisional Application No. 60/362,251, filed Mar. 5, 2002.[0001]
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention [0002]
  • The present invention relates generally to mobile computing and more specifically to roaming of mobile nodes. [0003]
  • 2. Description of the Related Art [0004]
  • Mobile IP is a protocol that allows laptop computers and other mobile computer units (“mobile nodes”) to roam between various sub-networks while maintaining Internet and/or WAN connectivity. Without Mobile IP or similar protocols a mobile node would be unable to stay connected while roaming from one location serviced by one sub-network to another location being serviced by a different sub-network. This is because 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 that is normally attached to one node and roam so that it passes through different sub-networks, the roaming computer cannot use its home base IP address. As a result, a businessperson traveling across the country cannot travel with his or her computer across geographically disparate network segments or wireless nodes while maintaining Internet connectivity. This is not acceptable in the age of portable computational devices. [0005]
  • To address this problem, the Mobile IP protocol has been developed and implemented. An implementation of Mobile IP is described in RFC 3344, “IP Mobility Support for IPv4” of the Network Working Group, C. Perkins, Ed., January 2002. Mobile IP is also described in the text “Mobile IP, The Internet Unplugged” by J. Solomon, Prentice Hall, 1998. Both of these references are incorporated herein by reference in their entireties and for all purposes. [0006]
  • The Mobile IP process and environment are illustrated in FIG. 1. A Mobile IP environment [0007] 100 includes the Internet (or a WAN) 105 over which a mobile node 110 can communicate via mediation by a home agent 115 or a foreign agent 120. Typically, the home agent 115 and foreign agent 120 are routers or other network connection devices performing appropriate Mobile IP functions as implemented by software, hardware, and/or firmware. Note the overall network topology is arbitrary, and elements such as the home agent 115 need not directly connect to the Internet 105. For example, the home agent 115 may be connected through another router R2 125. Router R2 125 may, in turn, connect one or more other routers R3 130 with the Internet 105.
  • When mobile node [0008] 110 is plugged into its home network segment 135 it connects with the Internet 105 through its designated home agent 115. When the mobile node 110 roams, it can be connected to a remote network segment 140 and communicate through the available foreign agent 120. Other nodes, such as a PC 145, on remote network segment 140 also communicate with the Internet 105 through foreign agent 120. Presumably, there are many foreign agents available at geographically disparate locations to allow wide spread Internet connection via the Mobile IP protocol.
  • Mobile node [0009] 110 may identify foreign agent 120 through various agent solicitations and agent advertisements that form part of the Mobile IP protocol. When mobile node 110 engages with remote network segment 140, it composes a registration request for the home agent 115 to bind the mobile node's 110 current location with its home location. Foreign agent 120 then relays the registration request 150 to home agent 115. During the registration process, the home agent 115 and the mobile node 110 may then negotiate the conditions of the mobile node's 110 attachment to foreign agent 120. For example, the mobile node 110 may request a registration lifetime of 5 hours, but the home agent 115 may grant only a 3 hour period. When the negotiation is successfully completed, home agent 115 updates an internal “mobility binding table” which links the mobile node's 110 current location via its care-of address (e.g., a co-located care-of address or the foreign agent's IP address) to the identity (e.g., home address) of the mobile node 110. Further, if the mobile node 110 registered via foreign agent 120, the foreign agent 120 updates an internal “visitor table” which specifies the mobile node address, home agent address, etc. The home agent's 115 association between a mobile node's home base IP address, its current care-of address, and the remaining lifetime of that association is referred to as a binding.
  • If mobile node [0010] 110 wanted to send a message to a correspondent node 155 from its new location, the mobile node 110 would forward a packetized output message 160 through the foreign agent 120 over the Internet 105 to the correspondent node 155 according to standard Internet protocols. However, if the correspondent node 155 wanted to send a message 165 to the mobile node 110—whether in reply to a message from the mobile node 110 or for any other reason—the correspondent node 155 addresses that message to the IP address of the mobile node 110 as if the mobile node 110 were on the home network segment 135. The packets of the message from the correspondent node 155 are forwarded over the Internet 105 to the router R2 125 and ultimately to the home agent 115.
  • From the home agent's [0011] 115 mobility binding table, the home agent 115 recognizes that the mobile node 110 is no longer attached to the home network segment 135. The home agent 115 then encapsulates the packets from correspondent node 155 (which are addressed to the mobile node 110 on the home network segment 135) according to the Mobile IP protocol, and forwards these encapsulated packets 170 to the appropriate care-of address for mobile node 110. If the care-of address is the IP address of the foreign agent 120 the foreign agent 120 strips the encapsulation and forwards the message to the mobile node 110 on the remote network segment 140. The packet forwarding mechanism implemented by the home agent 115 to the foreign agent 120 is often referred to as “tunneling.”
  • As set forth in RFC 3344, the Mobile IP specification, the mobile node [0012] 110 can be statically provisioned with its home address or request home address assignment. Home address assignment is typically requested by setting the home address field of the registration request to 0.0.0.0 and using a mobile node network address identifier (NAI) extension to identify itself. NAI is described in RFC 2794 of the Network Working Group, P. Calhoun and C. Perkins, March 2000, incorporated herein by reference in its entireties and for all purposes. After receiving and authenticating such a registration request, the home agent is expected to assign a home address to the mobile node in the registration reply.
  • One proposal for home address assignment by the home agent is described in the IETF working group draft, “Mobile IP Agents as DHCP Proxies,” S. Glass, draft-glass-mobileip-agent-dhcp-proxy-01.txt, Mar. 2, 2000, incorporated herein by reference in its entirety and for all purposes. In that draft, the home agent behaves as a DHCP proxy agent, acting on behalf of the mobile node. [0013]
  • DHCP is based on the Bootstrap Protocol (BOOTP), an Internet protocol that enables a diskless workstation to discover its own IP address. DHCP is described in RFC 2131 of the Network Working Group, R. Droms, March 1997, and BOOTP is described in RFC 951 of the Network Working Group, B. Croft, September 1985, both references incorporated herein by reference in their entirety and for all purposes. RFC 2131 defines a DHCP server as a host that provides initialization parameters through DHCP. Essentially, a DHCP server allows IP addresses to be dynamically assigned to devices on a network. Dynamic addressing simplifies network administration because the software keeps track of IP addresses rather than requiring an administrator to statically provision the IP address for every device on the network. Current Microsoft Windows® operating systems have integrated DHCP client support. [0014]
  • Although Mobile IP has many well-defined mechanisms that are useful for mobility services, RFC 3344 also states, “When connected to its home network, a mobile node operates without the support of mobility services. That is, it operates in the same way as any other (fixed) host or router.” However, the mechanism by which a mobile node achieves this operation has not been described. Furthermore, once a mobile node is connected to home network, and is acting as “any other (fixed) host or router,” no mechanisms are available to allow the mobile node to roam. [0015]
  • SUMMARY OF THE INVENTION
  • The present invention provides methods and apparatuses for mobile nodes home address management. In one embodiment a mobile node attaches itself to the mobile node's home agent network segment. The mobile node then performs agent discovery procedures and sends out a registration request to the home agent, requesting a home address. The mobile node then receives a registration reply with an allocated home address. The reply indicates that no mobility bindings have been created since the mobile node is on its home network, and the mobile node is responsible for its own DHCP address management. [0016]
  • In another embodiment a home agent receives a registration request for a mobile node for which mobility bindings do not exist. The registration request indicates that a dynamically assigned home address has already been acquired. The home agent then authenticates the mobile node and creates mobility bindings for the mobile node. Afterwards, the home agent sends a registration reply to the mobile node. [0017]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram of a Mobile IP environment; [0018]
  • FIG. 2 is a block diagram illustrating an exemplary environment in which the present invention may be implemented; [0019]
  • FIG. 3 is a control flow diagram illustrating a method of allowing a mobile node to use the same IP address it was initially assigned with DHCP for Mobile IP purposes when the mobile node boots up on the home agent's network segment; [0020]
  • FIG. 4 is a diagram illustrating an exemplary network device in which various embodiments of the invention may be implemented. [0021]
  • FIG. 5 is a diagram illustrating a network device suitable for implementing the techniques of the present invention. [0022]
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • In the following description, numerous specific details are set forth 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 to avoid unnecessarily obscuring the present invention. [0023]
  • The present invention allows a mobile node that connects to a home network to use mobility services if the mobile node later roams. A home agent is able to authenticate a roaming mobile node, even though mobility bindings were not created. Methods by which a home agent can accomplish this include use of cached information and performing a DHCP INFORM on the mobile node's IP address. [0024]
  • FIG. 2 is a block diagram illustrating an exemplary environment in which the present invention may be implemented. A network [0025] 205 contains a home agent 210, a foreign agent 215, a DHCP server 220, and a mobile node 225. The mobile node 225 can attach itself to the home agent 210 via the home agent network segment 230, which may have several different ports 235 and 240, and the mobile node 225 can attach itself to the foreign agent 215 via the foreign agent network segment 245.
  • FIG. 3 is a control flow diagram illustrating an implementation of the invention. Steps performed by the mobile node [0026] 225, the home agent 210 and DHCP server 220 are represented by corresponding vertical lines 305, 310, and 315.
  • At [0027] 320 the mobile node 225 and the home agent 210 perform standard agent discovery procedures (e.g., the home agent 210 sends an agent advertisement, either on its own or in response to an agent solicitation from the mobile node 225). Once agent discovery is complete, at 325 the mobile node 225 sends out a registration request, similar to a standard registration request that the mobile node 225 sends out when it finds itself on the foreign agent network segment 245. The mobile node 225 could append a DHCP extension that indicates that the mobile node 225 wants an address allocated via DHCP.
  • Additionally, the DHCP extension can have a bit indicating that the mobile node [0028] 225 wants to manage its home address via DHCP. Upon receipt of the registration request, the home agent 210 does DHCP address allocation for the mobile node 225. As requested by the mobile node 225, the home agent 210 sends the DHCP server 220 information, lease lifetime, and subnet mask information in a DHCP extension appended to the registration reply back to the mobile node 225. When the mobile node 225 is attached via the home agent network segment 230 and the mobile node 225 asked for DHCP information indicating that it is DHCP aware, the home agent 210 can specifically ask the mobile node 225 to manage its own home address via DHCP. The home agent 210 informs the mobile node 225 of this by setting the M bit in the DHCP extension in the registration reply.
  • Depending on the specific embodiment, the home agent [0029] 210 can process the message several different ways at 330. For example, if the home agent 210 had cached the mobile node's 225 original DHCP request, as described in U.S. application Ser. No. 10/241,969, the home agent 210 could immediately submit a registration reply back to the mobile node 225, reusing the DHCP address as the mobile node's 225 home address.
  • Other methods of assigning a home address to the mobile node [0030] 225 include referring to a static internal table of available IP addresses, using an AAA server or using a DHCP server 220 to assign a home address. If the mobile node 225 did not identify a source IP address (i.e., it did not receive a prior DHCP address), the home agent 210 could use the gateway interface address (giaddr) of the registration request at 325 in its communications with the DHCP server 220 at 335. Communications with the DHCP server 220 could then include a DHCP discover, a DHCP offer, a DHCP request and a DHCP acknowledgement.
  • Once the home agent [0031] 210 determines a home address for the mobile node 225, it can optionally cache the home address, the NAI and the MAC address. However, no mobility bindings need to be created at 330 since the mobile node is on its home network.
  • At [0032] 340 the home agent 210 sends a registration reply to the mobile node 225. The registration reply should contain the NAI, the home address of the mobile node 225, the address of the home agent 210, and a lifetime.
  • At [0033] 345 a zero lifetime will alert the mobile node 225 that the home agent 210 has not created any mobility bindings, and the M bit in the DHCP extension relays that the mobile node 225 is responsible for its own DHCP address management.
  • Any number of other methods could also be used to alert the mobile node of its address management responsibilities. For example, an extension to the registration reply could also alert the mobile node [0034] 225 of its responsibilities. Alternatively, the mobile node 225 could have determined that it was in its home network segment 230 from the agent discovery procedures at 320.
  • Once the mobile node [0035] 225 is alerted to its address management responsibilities, the mobile node 225 will also need to have the IP address of the DHCP server 220 and the net prefix in order to perform these responsibilities. If the mobile node 225 did not already receive the information in accordance with the method described in U.S. application Ser. No. 10/241,969 or through some other means, the home agent 210 could include the DHCP server 220 address and the net prefix in the registration reply. Therefore, for as long as the mobile node 225 was attached to the appropriate port 235 on the home agent network segment 230, it would act as any other fixed host.
  • At [0036] 350 the mobile node 225 roams to another port 240 on the home agent network segment 230. At 355 the mobile node 225 conducts agent discovery procedures and detects movement. At 360 the mobile node 225 sends a registration request to the home agent 210 with an appended DHCP extension, indicating that the home address was already acquired via DHCP by setting the H bit in the DHCP extension. Since the NAI is mapped to the client ID in DHCP, the home agent 210 would require the DHCP information in order to authorize the mobile node's 225 home address. The mobile node 225 might have to supply the information (DHCP server address, subnet mask etc), depending on whether the home agent 210 previously cached the information.
  • At [0037] 365 the home agent 210 processes the registration request. In order to authenticate the request, the home agent 210 would either refer to its cache or, if no cache was kept, at 370 the home agent 210 could perform a DHCP INFORM on the mobile node's 225 IP address in order to get the required information. If the home agent 210 referred to its cache to authenticate the mobile node 225, it could also ping the home address to ensure the DHCP server 220 did not give out the address to another device in the interim. Once the mobile node 225 is authenticated, the home agent 210 would create mobility bindings. However, since the mobile node 225 was still connected to the home agent 210, no tunnels need to be created.
  • At [0038] 375 the home agent 210 sends a registration reply to the mobile node 225, and the mobile node 225 would have access to fill mobility services. If the DHCP TLV M bit was set, the mobile node 225 could continue to renew its lease with the DHCP address directly. Otherwise the home agent 210 would provide DHCP proxy services.
  • At [0039] 380 the mobile node 225 roams back to the original port 235 on the home agent network segment 230. At 385 the mobile node 225 conducts agent discovery procedures and detects movement. At 390 the mobile node 225 sends a deregistration request to the home agent 210, requesting the home agent 210 delete its bindings so the mobile node 225 can act as any other fixed node.
  • At [0040] 395 the home agent 210 can delete the bindings to the mobile node 225 If a tunnel was created, it would also be deleted. If the home agent 210 uses the cached information method for authenticating later registration requests, the home agent 210 might need to re-cache information relating to the mobile node 225. At 398 the home agent 210 sends a registration reply back to the mobile node 225. Once again, the mobile node 225 would be responsible for its DHCP management responsibilities.
  • FIG. 4 is a control flow diagram illustrating an implementation of the invention. Steps performed by the mobile node [0041] 225, the home agent 210, DHCP server 220 and foreign agent 215 are represented by corresponding vertical lines 305, 310, 315 and 405.
  • At [0042] 410 the mobile node 225 roams to the foreign agent network segment 245 from its original port 235 on the home agent network segment 230. It does not matter whether the mobile node 225 had previously roamed and deregistered (as described in FIG. 3) or whether the foreign agent network segment 245 is the mobile node's 225 first roam.
  • At [0043] 415 the mobile node 225 conducts agent discovery procedures and detects movement. At 420 the mobile node 225 sends a registration request with an appended DHCP extension to the home agent 210, indicating that the home address was already acquired by setting the H bit in the DHCP extension. Depending upon which scheme is being used, the mobile node 225 might also have to supply the DHCP information in order to authorize the mobile node's 225 home address.
  • At [0044] 425 the foreign agent 215 relays the registration request to the home agent 210. Once the home agent 210 receives the registration request at 430, it must authenticate the request. The home agent 210 would either refer to its cache or at 435 perform a DHCP INFORM on the mobile node's 225 IP address in order to get the required information. A ping on the mobile node's 225 IP address might also be appropriate. Once the mobile node 225 is authenticated, the home agent 210 would create mobility bindings and an appropriate tunnel.
  • At [0045] 440 the home agent 210 sends a registration reply to the foreign agent 215, which relays the registration reply to the mobile node 225 at 445. Once the mobile node 225 receives the registration reply it would have access to full mobility services.
  • 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. [0046]
  • 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, home agents, and foreign agents of this invention may be implemented in specially configured routers, switches or servers, such as specially configured router models 2600, 3200, 3600, 4500, 7200, and 7500 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. [0047]
  • Referring now to FIG. 5, a network device [0048] 500 suitable for implementing the techniques of the present invention includes a master central processing unit (CPU) 505, interfaces 510, memory 515 and a bus 520. When acting under the control of appropriate software or firmware, the CPU 505 may be responsible for implementing specific functions associated with the functions of a desired network device. For example, when configured as an intermediate router, the CPU 505 may be responsible for analyzing packets, encapsulating packets, and forwarding packets for transmission to a set-top box. The CPU 505 preferably accomplishes all these functions under the control of software including an operating system (e.g. Windows NT), and any appropriate applications software.
  • CPU [0049] 505 may include one or more processors such as those from the Motorola family of microprocessors or the MIPS family of microprocessors. In an alternative embodiment, the processor is specially designed hardware for controlling the operations of network device 500.
  • The interfaces [0050] 510 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 500. 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 CPU 405 to efficiently perform routing computations, network diagnostics, security functions, etc.
  • Although the system shown in FIG. 4 illustrates one specific network device of the present invention, it is by no means the only network device architecture on which the present invention can be implemented. For example, an architecture having a single processor that handles communications as well as routing computations, etc. is often used. Further, other types of interfaces and media could also be used with the network device. [0051]
  • Regardless of network device's configuration, it may employ one or more memories or memory modules (such as, for example, the memory [0052] 515) 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 traveling 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. [0053]
  • 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, the present invention is described as being configured to comply with Mobile IP standards in force as of the time this document was written. However, it should be understood that the invention is not limited to such implementations. 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. [0054]

Claims (33)

    What is claimed is:
  1. 1. A method of processing a registration request received from a mobile node for which mobility bindings are not available, comprising:
    receiving a registration request from the mobile node for which mobility bindings are not available, the registration request indicating that a dynamically assigned home address has already been acquired;
    authenticating the mobile node;
    creating mobility bindings; and
    sending a registration reply to the mobile node.
  2. 2. The method as recited in claim 1, wherein authenticating the mobile node includes referring to cached information about the mobile node.
  3. 3. The method as recited in claim 2, wherein the cached information was generated during a previous DHCP request from the mobile node.
  4. 4. The method as recited in claim 3, wherein a cached DHCP acknowledgement message was the cached information generated during a previous DHCP request from the mobile node.
  5. 5. The method as recited in claim 2, wherein the cached information was generated during a previous registration from the mobile node when the mobile node was on the home agent's network segment.
  6. 6. The method as recited in claim 5, wherein the previous registration included a lifetime value of zero.
  7. 7. The method as recited in claim 5, wherein the mobile node managed its own DHCP address in connection with the previous registration.
  8. 8. The method as recited in claim 7, wherein the mobile node was alerted to its DHCP address management responsibilities via a lifetime value of zero in the previous registration.
  9. 9. The method as recited in claim 7, wherein the mobile node was alerted to its DCHP address management responsibilities via an extension in the previous registration.
  10. 10. The method as recited in claim 9, wherein the extension in the previous registration was an M-bit.
  11. 11. The method as recited in claim 2, further comprising performing a ping operation on the home address.
  12. 12. The method as recited in claim 1, wherein the home address was previously acquired through a DHCP request, the DHCP request being initiated by a previous registration request in which the mobile node was on the home agent's network segment.
  13. 13. The method as recited in claim 12, wherein the DHCP request used the mobile node's gateway interface address.
  14. 14. The method as recited in claim 1, wherein the registration request includes information relating to DHCP address management.
  15. 15. The method as recited in claim 1, wherein authenticating the mobile node includes performing a DHCP INFORM on the home address.
  16. 16. In a mobile node, a method of registration on a network segment of the mobile node's home agent comprising:
    performing agent discovery procedures;
    sending a registration request; and
    receiving a registration reply indicating that no mobility bindings have been created and the mobile node is responsible for its own DHCP address management.
  17. 17. A home agent comprising:
    a processor;
    memory, operably connected with the processor; and
    a network interface, operably connected with the processor;
    wherein the processor is operable to perform instructions including
    receiving a registration request from the mobile node for which mobility bindings are not available, the registration request indicating that a dynamically assigned home address has already been acquired;
    authenticating the mobile node;
    creating mobility bindings; and
    sending a registration reply to the mobile node.
  18. 18. The home agent of claim 17, wherein authenticating the mobile node includes referring to cached information about the mobile node.
  19. 19. The home agent of claim 18, wherein the cached information was generated during a previous DHCP request from the mobile node.
  20. 20. The home agent of claim 19, wherein a cached DHCP acknowledgement message was the cached information generated during a previous DHCP request from the mobile node.
  21. 21. The home agent of claim 18, wherein the cached information was generated during a previous registration from the mobile node when the mobile node was on the home agent's network segment.
  22. 22. The home agent of claim 21, wherein the previous registration included a lifetime value of zero.
  23. 23. The home agent of claim 21, wherein the mobile node managed its own DHCP address in connection with the previous registration.
  24. 24. The home agent of claim 21, wherein the mobile node was alerted to its DHCP address management responsibilities via a lifetime value of zero in the previous registration.
  25. 25. The home agent of claim 18, wherein the processor is operable to additionally perform instructions including
    performing a ping operation on the home address.
  26. 26. The home agent of claim 17, wherein the home address was previously acquired through a DHCP request, the DHCP request being initiated by a previous registration request in which the mobile node was on the home agent's network segment.
  27. 27. The home agent of claim 26, wherein the DHCP request used the mobile node's gateway interface address.
  28. 28. The home agent of claim 17, wherein the registration request includes information relating to DHCP address management.
  29. 29. The home agent of claim 17, wherein authenticating the mobile node includes performing a DHCP INFORM on the home address.
  30. 30. A mobile node comprising:
    a processor;
    memory, operably connected with the processor; and
    a network interface, operably connected with the processor;
    wherein the processor is operable to perform instructions including
    performing agent discovery procedures;
    sending a registration request; and
    receiving a registration reply indicating that no mobility bindings have been created and the mobile node is responsible for its own DHCP address management;
    wherein the instructions are performed when the mobile node is attached to the mobile node's home agent network segment.
  31. 31. A home agent comprising:
    means for receiving a registration request from the mobile node for which mobility bindings are not available, the registration request indicating that a dynamically assigned home address has already been acquired;
    means for authenticating the mobile node;
    means for creating mobility bindings; and
    menas for sending a registration reply to the mobile node
  32. 32. A mobile node comprising:
    means for performing agent discovery procedures;
    means for sending a registration request; and
    means for receiving a registration reply indicating that no mobility bindings have been created and the mobile node is responsible for its own DHCP address management;
    wherein each of the means are performed when the mobile node is attached to the mobile node's home agent network segment.
  33. 33. In a home agent, a method of processing a registration request received from a mobile node, comprising:
    receiving a request for assignment of a DHCP address, the request being received from a mobile node;
    determining whether the mobile node is on its home network segment;
    informing the mobile node that it is responsible for its own DHCP address management if the mobile node is on its home network address.
US10300437 2002-03-05 2002-11-19 DHCP based home address management of mobile IP clients Active 2024-09-11 US7461169B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US36225102 true 2002-03-05 2002-03-05
US10241969 US8090828B2 (en) 2002-03-05 2002-09-11 Method and apparatus for reusing DHCP addresses in home addresses of mobile IP clients
US10300437 US7461169B2 (en) 2002-03-05 2002-11-19 DHCP based home address management of mobile IP clients

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US10300437 US7461169B2 (en) 2002-03-05 2002-11-19 DHCP based home address management of mobile IP clients

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10241969 Continuation-In-Part US8090828B2 (en) 2002-03-05 2002-09-11 Method and apparatus for reusing DHCP addresses in home addresses of mobile IP clients

Publications (2)

Publication Number Publication Date
US20030217180A1 true true US20030217180A1 (en) 2003-11-20
US7461169B2 US7461169B2 (en) 2008-12-02

Family

ID=46281564

Family Applications (1)

Application Number Title Priority Date Filing Date
US10300437 Active 2024-09-11 US7461169B2 (en) 2002-03-05 2002-11-19 DHCP based home address management of mobile IP clients

Country Status (1)

Country Link
US (1) US7461169B2 (en)

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030229697A1 (en) * 2002-06-10 2003-12-11 3Com Corporation Method and apparatus for global server load balancing
US20040179539A1 (en) * 2003-03-14 2004-09-16 Yukiko Takeda Communication system, gateway equipment, communication method and authentication method
US20040218558A1 (en) * 2003-02-27 2004-11-04 Interactive People Unplugged Ab Dynamic IP address allocation
US20050086502A1 (en) * 2003-10-16 2005-04-21 Ammar Rayes Policy-based network security management
WO2005053196A2 (en) * 2003-11-26 2005-06-09 Nokia Corporation Method and apparatus to provide efficient routing of packets for a network initiated data session
US20050259626A1 (en) * 2004-05-21 2005-11-24 Nokia Corporation Method of communication
WO2006025651A1 (en) * 2004-08-28 2006-03-09 Samsung Electronics Co., Ltd. Method and device for universal plug and play communications
US20070297396A1 (en) * 2006-06-22 2007-12-27 Avigdor Eldar Secure and automatic provisioning of computer systems having embedded network devices
US7447162B1 (en) 2002-03-05 2008-11-04 Cisco Technology, Inc. Methods and apparatus for anchoring of mobile nodes using DNS
US7461169B2 (en) 2002-03-05 2008-12-02 Cisco Technology, Inc. DHCP based home address management of mobile IP clients
US7577427B2 (en) * 2003-11-05 2009-08-18 At&T Intellectual Property I, L.P. System and method of transitioning between cellular and voice over internet protocol communication
US20090238099A1 (en) * 2008-03-24 2009-09-24 Qualcomm Incorporated Dynamic home network assignment
US20090254668A1 (en) * 2008-04-03 2009-10-08 Samsung Electronics Co. Ltd. System and method for searching for session id in wireless mobile ip communication system
US7607021B2 (en) 2004-03-09 2009-10-20 Cisco Technology, Inc. Isolation approach for network users associated with elevated risk
US7616950B2 (en) 2003-09-04 2009-11-10 At&T Intellectual Property I, L.P. Call forwarding control device and method of call management
WO2010022562A1 (en) * 2008-08-29 2010-03-04 上海贝尔阿尔卡特股份有限公司 A method and foreign agent group for registering to a home agent of a mobile node
US20110179189A1 (en) * 2008-12-26 2011-07-21 Canon Kabushiki Kaisha Communication apparatus, method of controlling the same, program, and storage medium
US8090828B2 (en) 2002-03-05 2012-01-03 Cisco Technology, Inc. Method and apparatus for reusing DHCP addresses in home addresses of mobile IP clients
US20140177553A1 (en) * 2002-09-24 2014-06-26 Orange Sa Method and apparatus for data transfer in a packet-switched network

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030224788A1 (en) * 2002-03-05 2003-12-04 Cisco Technology, Inc. Mobile IP roaming between internal and external networks
US7668174B1 (en) * 2002-10-17 2010-02-23 Cisco Technology, Inc. Methods and apparatus for home address management at home agent for NAI based mobile nodes
US7643451B2 (en) * 2004-10-15 2010-01-05 Nortel Networks Limited Method and apparatus for extending a mobile unit data path between access points
US7463607B2 (en) * 2005-04-15 2008-12-09 Intel Corporation Apparatus, system and method capable of pre-allocating and communicating IP address information during wireless communication
CN1929497B (en) * 2005-09-07 2010-07-07 华为技术有限公司 Method and system for obtaining moving nodes local proxy information
KR100757896B1 (en) * 2006-05-24 2007-09-11 한국전자통신연구원 System and method for remote home-service download in home network system
US8488571B2 (en) * 2007-11-28 2013-07-16 Alcatel Lucent Method and apparatus for managing an IP address space of an address server in a mobility network
EP2091204A1 (en) 2008-02-18 2009-08-19 Panasonic Corporation Home agent discovery upon changing the mobility management scheme

Citations (43)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6161123A (en) * 1997-05-06 2000-12-12 Intermec Ip Corporation Providing reliable communication over an unreliable transport layer in a hand-held device using a persistent session
US6163843A (en) * 1996-10-25 2000-12-19 Kabushiki Kaisha Toshiba Packet inspection device, mobile computer and packet transfer method in mobile computing with improved mobile computer authenticity check scheme
US6167513A (en) * 1996-11-01 2000-12-26 Kabushiki Kaisha Toshiba Mobile computing scheme using encryption and authentication processing based on mobile computer location and network operating policy
US6230012B1 (en) * 1998-08-07 2001-05-08 Qualcomm Incorporated IP mobility support using proxy mobile node registration
US6233616B1 (en) * 1997-10-24 2001-05-15 William J. Reid Enterprise network management using directory containing network addresses of users obtained through DHCP to control routers and servers
US20010014917A1 (en) * 2000-02-15 2001-08-16 Kabushiki Kaisha Toshiba Position identifier management apparatus and method, mobile computer, and position identifier processing method
US6339830B1 (en) * 1997-06-13 2002-01-15 Alcatel Internetworking, Inc. Deterministic user authentication service for communication network
US20020052954A1 (en) * 2000-04-27 2002-05-02 Polizzi Kathleen Riddell Method and apparatus for implementing a dynamically updated portal page in an enterprise-wide computer system
US20020058480A1 (en) * 2000-11-13 2002-05-16 Matsushita Electri Industrial Co., Ltd. Base station apparatus, mobile terminal apparatus and wireless access system using the apparatuses
US20020073182A1 (en) * 2000-12-08 2002-06-13 Zakurdaev Maxim V. Method and apparatus for a smart DHCP relay
US20020089958A1 (en) * 1997-10-14 2002-07-11 Peretz Feder Point-to-point protocol encapsulation in ethernet frame
US6421714B1 (en) * 1997-10-14 2002-07-16 Lucent Technologies Efficient mobility management scheme for a wireless internet access system
US6427170B1 (en) * 1998-12-08 2002-07-30 Cisco Technology, Inc. Integrated IP address management
US20020114323A1 (en) * 2001-02-09 2002-08-22 Kuntal Chowdhury Method and apparatus for dynamically assigning a home agent
US6442616B1 (en) * 1997-01-16 2002-08-27 Kabushiki Kaisha Toshiba Method and apparatus for communication control of mobil computers in communication network systems using private IP addresses
US6463134B1 (en) * 1999-08-03 2002-10-08 Matsushita Electric Industrial Co., Ltd. Easy response system
US6473411B1 (en) * 1997-05-12 2002-10-29 Kabushiki Kaisha Toshiba Router device, datagram transfer method and communication system realizing handoff control for mobile terminals
US20030018810A1 (en) * 2000-10-18 2003-01-23 Telefonaktiebolaget L M Ericsson (Publ) Seamless handoff in mobile IP
US6515974B1 (en) * 1998-06-16 2003-02-04 Kabushiki Kaisha Toshiba Mobile computer communication scheme supporting moving among networks of different address systems
US20030058853A1 (en) * 2001-09-26 2003-03-27 Eugene Gorbatov Method and apparatus for mobile device roaming in wireless local area network
US6567664B1 (en) * 1999-06-02 2003-05-20 Nokia Corporation Registration for mobile nodes in wireless internet protocols
US20030101243A1 (en) * 2001-11-27 2003-05-29 Donahue David B. System and method for automatic confuguration of a bi-directional IP communication device
US20030104814A1 (en) * 2001-11-30 2003-06-05 Docomo Communications Laboratories Usa Low latency mobile initiated tunneling handoff
US20030119506A1 (en) * 2001-12-20 2003-06-26 Sandeep Singhai Efficient re-registration of mobile IP nodes
US20030126262A1 (en) * 2001-12-27 2003-07-03 Fuji Xerox Co., Ltd. Method for assigning setting information for conection to external network
US6636894B1 (en) * 1998-12-08 2003-10-21 Nomadix, Inc. Systems and methods for redirecting users having transparent computer access to a network using a gateway device having redirection capability
US6654359B1 (en) * 1998-12-11 2003-11-25 Lucent Technologies Inc. Wireless access to packet-based networks
US6681259B1 (en) * 1998-05-12 2004-01-20 Nokia Mobile Phones Ltd Method for coupling a wireless terminal to a data transmission network and a wireless terminal
US6687245B2 (en) * 2001-04-03 2004-02-03 Voxpath Networks, Inc. System and method for performing IP telephony
US20040072557A1 (en) * 2001-02-09 2004-04-15 Toni Paila Method, network access element and mobile node for service advertising and user authorization in a telecommunication system
US6742036B1 (en) * 1997-12-19 2004-05-25 Siemens Aktiengesellschaft Method for supporting mobility on the internet
US6766168B1 (en) * 1999-02-12 2004-07-20 Lg Information & Communications, Ltd. Packet data service network in a mobile radio communication network and method of operating a packet data service using the packet data service network
US6771623B2 (en) * 2000-12-01 2004-08-03 Telefonaktiebolaget Lm Ericsson (Publ) Method for ensuring reliable mobile IP service
US6778528B1 (en) * 2000-05-17 2004-08-17 Cisco Technology, Inc. Dial-out with dynamic IP address assignment
US6839337B2 (en) * 2001-12-10 2005-01-04 Motorola, Inc. Binding proxy for mobile devices in a data network
US6892069B1 (en) * 1997-12-17 2005-05-10 British Telecommunications, Plc Proxy routing
US6954790B2 (en) * 2000-12-05 2005-10-11 Interactive People Unplugged Ab Network-based mobile workgroup system
US6973528B2 (en) * 2002-05-22 2005-12-06 International Business Machines Corporation Data caching on bridge following disconnect
US6973057B1 (en) * 1999-01-29 2005-12-06 Telefonaktiebolaget L M Ericsson (Publ) Public mobile data communications network
US20050286466A1 (en) * 2000-11-03 2005-12-29 Tagg James P System for providing mobile VoIP
US7031275B1 (en) * 2000-12-28 2006-04-18 Utstarcom, Inc. Address management for mobile nodes
US7042988B2 (en) * 2001-09-28 2006-05-09 Bluesocket, Inc. Method and system for managing data traffic in wireless networks
US7152117B1 (en) * 2001-10-04 2006-12-19 Cisco Technology, Inc. Techniques for dynamic host configuration using overlapping network

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030224788A1 (en) 2002-03-05 2003-12-04 Cisco Technology, Inc. Mobile IP roaming between internal and external networks
US8090828B2 (en) 2002-03-05 2012-01-03 Cisco Technology, Inc. Method and apparatus for reusing DHCP addresses in home addresses of mobile IP clients
US7461169B2 (en) 2002-03-05 2008-12-02 Cisco Technology, Inc. DHCP based home address management of mobile IP clients

Patent Citations (43)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6163843A (en) * 1996-10-25 2000-12-19 Kabushiki Kaisha Toshiba Packet inspection device, mobile computer and packet transfer method in mobile computing with improved mobile computer authenticity check scheme
US6167513A (en) * 1996-11-01 2000-12-26 Kabushiki Kaisha Toshiba Mobile computing scheme using encryption and authentication processing based on mobile computer location and network operating policy
US6442616B1 (en) * 1997-01-16 2002-08-27 Kabushiki Kaisha Toshiba Method and apparatus for communication control of mobil computers in communication network systems using private IP addresses
US6161123A (en) * 1997-05-06 2000-12-12 Intermec Ip Corporation Providing reliable communication over an unreliable transport layer in a hand-held device using a persistent session
US6473411B1 (en) * 1997-05-12 2002-10-29 Kabushiki Kaisha Toshiba Router device, datagram transfer method and communication system realizing handoff control for mobile terminals
US6339830B1 (en) * 1997-06-13 2002-01-15 Alcatel Internetworking, Inc. Deterministic user authentication service for communication network
US6421714B1 (en) * 1997-10-14 2002-07-16 Lucent Technologies Efficient mobility management scheme for a wireless internet access system
US20020089958A1 (en) * 1997-10-14 2002-07-11 Peretz Feder Point-to-point protocol encapsulation in ethernet frame
US6233616B1 (en) * 1997-10-24 2001-05-15 William J. Reid Enterprise network management using directory containing network addresses of users obtained through DHCP to control routers and servers
US6892069B1 (en) * 1997-12-17 2005-05-10 British Telecommunications, Plc Proxy routing
US6742036B1 (en) * 1997-12-19 2004-05-25 Siemens Aktiengesellschaft Method for supporting mobility on the internet
US6681259B1 (en) * 1998-05-12 2004-01-20 Nokia Mobile Phones Ltd Method for coupling a wireless terminal to a data transmission network and a wireless terminal
US6515974B1 (en) * 1998-06-16 2003-02-04 Kabushiki Kaisha Toshiba Mobile computer communication scheme supporting moving among networks of different address systems
US6230012B1 (en) * 1998-08-07 2001-05-08 Qualcomm Incorporated IP mobility support using proxy mobile node registration
US6636894B1 (en) * 1998-12-08 2003-10-21 Nomadix, Inc. Systems and methods for redirecting users having transparent computer access to a network using a gateway device having redirection capability
US6427170B1 (en) * 1998-12-08 2002-07-30 Cisco Technology, Inc. Integrated IP address management
US6654359B1 (en) * 1998-12-11 2003-11-25 Lucent Technologies Inc. Wireless access to packet-based networks
US6973057B1 (en) * 1999-01-29 2005-12-06 Telefonaktiebolaget L M Ericsson (Publ) Public mobile data communications network
US6766168B1 (en) * 1999-02-12 2004-07-20 Lg Information & Communications, Ltd. Packet data service network in a mobile radio communication network and method of operating a packet data service using the packet data service network
US6567664B1 (en) * 1999-06-02 2003-05-20 Nokia Corporation Registration for mobile nodes in wireless internet protocols
US6463134B1 (en) * 1999-08-03 2002-10-08 Matsushita Electric Industrial Co., Ltd. Easy response system
US20010014917A1 (en) * 2000-02-15 2001-08-16 Kabushiki Kaisha Toshiba Position identifier management apparatus and method, mobile computer, and position identifier processing method
US20020052954A1 (en) * 2000-04-27 2002-05-02 Polizzi Kathleen Riddell Method and apparatus for implementing a dynamically updated portal page in an enterprise-wide computer system
US6778528B1 (en) * 2000-05-17 2004-08-17 Cisco Technology, Inc. Dial-out with dynamic IP address assignment
US20030018810A1 (en) * 2000-10-18 2003-01-23 Telefonaktiebolaget L M Ericsson (Publ) Seamless handoff in mobile IP
US20050286466A1 (en) * 2000-11-03 2005-12-29 Tagg James P System for providing mobile VoIP
US20020058480A1 (en) * 2000-11-13 2002-05-16 Matsushita Electri Industrial Co., Ltd. Base station apparatus, mobile terminal apparatus and wireless access system using the apparatuses
US6771623B2 (en) * 2000-12-01 2004-08-03 Telefonaktiebolaget Lm Ericsson (Publ) Method for ensuring reliable mobile IP service
US6954790B2 (en) * 2000-12-05 2005-10-11 Interactive People Unplugged Ab Network-based mobile workgroup system
US20020073182A1 (en) * 2000-12-08 2002-06-13 Zakurdaev Maxim V. Method and apparatus for a smart DHCP relay
US7031275B1 (en) * 2000-12-28 2006-04-18 Utstarcom, Inc. Address management for mobile nodes
US20020114323A1 (en) * 2001-02-09 2002-08-22 Kuntal Chowdhury Method and apparatus for dynamically assigning a home agent
US20040072557A1 (en) * 2001-02-09 2004-04-15 Toni Paila Method, network access element and mobile node for service advertising and user authorization in a telecommunication system
US6687245B2 (en) * 2001-04-03 2004-02-03 Voxpath Networks, Inc. System and method for performing IP telephony
US20030058853A1 (en) * 2001-09-26 2003-03-27 Eugene Gorbatov Method and apparatus for mobile device roaming in wireless local area network
US7042988B2 (en) * 2001-09-28 2006-05-09 Bluesocket, Inc. Method and system for managing data traffic in wireless networks
US7152117B1 (en) * 2001-10-04 2006-12-19 Cisco Technology, Inc. Techniques for dynamic host configuration using overlapping network
US20030101243A1 (en) * 2001-11-27 2003-05-29 Donahue David B. System and method for automatic confuguration of a bi-directional IP communication device
US20030104814A1 (en) * 2001-11-30 2003-06-05 Docomo Communications Laboratories Usa Low latency mobile initiated tunneling handoff
US6839337B2 (en) * 2001-12-10 2005-01-04 Motorola, Inc. Binding proxy for mobile devices in a data network
US20030119506A1 (en) * 2001-12-20 2003-06-26 Sandeep Singhai Efficient re-registration of mobile IP nodes
US20030126262A1 (en) * 2001-12-27 2003-07-03 Fuji Xerox Co., Ltd. Method for assigning setting information for conection to external network
US6973528B2 (en) * 2002-05-22 2005-12-06 International Business Machines Corporation Data caching on bridge following disconnect

Cited By (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8090828B2 (en) 2002-03-05 2012-01-03 Cisco Technology, Inc. Method and apparatus for reusing DHCP addresses in home addresses of mobile IP clients
US7461169B2 (en) 2002-03-05 2008-12-02 Cisco Technology, Inc. DHCP based home address management of mobile IP clients
US7447162B1 (en) 2002-03-05 2008-11-04 Cisco Technology, Inc. Methods and apparatus for anchoring of mobile nodes using DNS
US7305429B2 (en) * 2002-06-10 2007-12-04 Utstarcom, Inc. Method and apparatus for global server load balancing
US20030229697A1 (en) * 2002-06-10 2003-12-11 3Com Corporation Method and apparatus for global server load balancing
US20140177553A1 (en) * 2002-09-24 2014-06-26 Orange Sa Method and apparatus for data transfer in a packet-switched network
US9949238B2 (en) * 2002-09-24 2018-04-17 3G Licensing S.A. Method and apparatus for data transfer in a packet-switched network
US20040218558A1 (en) * 2003-02-27 2004-11-04 Interactive People Unplugged Ab Dynamic IP address allocation
US20040179539A1 (en) * 2003-03-14 2004-09-16 Yukiko Takeda Communication system, gateway equipment, communication method and authentication method
US7328014B2 (en) * 2003-03-14 2008-02-05 Hitachi, Ltd. Communication system, gateway equipment, communication method and authentication method
US7616950B2 (en) 2003-09-04 2009-11-10 At&T Intellectual Property I, L.P. Call forwarding control device and method of call management
US7237267B2 (en) 2003-10-16 2007-06-26 Cisco Technology, Inc. Policy-based network security management
US20050086502A1 (en) * 2003-10-16 2005-04-21 Ammar Rayes Policy-based network security management
US7885657B2 (en) 2003-11-05 2011-02-08 At&T Intellectual Property I, L.P. System and method of transitioning between cellular and voice over internet protocol communication
US7577427B2 (en) * 2003-11-05 2009-08-18 At&T Intellectual Property I, L.P. System and method of transitioning between cellular and voice over internet protocol communication
WO2005053196A3 (en) * 2003-11-26 2009-04-09 Sarvesh Asthana Method and apparatus to provide efficient routing of packets for a network initiated data session
WO2005053196A2 (en) * 2003-11-26 2005-06-09 Nokia Corporation Method and apparatus to provide efficient routing of packets for a network initiated data session
US7607021B2 (en) 2004-03-09 2009-10-20 Cisco Technology, Inc. Isolation approach for network users associated with elevated risk
US20050259626A1 (en) * 2004-05-21 2005-11-24 Nokia Corporation Method of communication
WO2006025651A1 (en) * 2004-08-28 2006-03-09 Samsung Electronics Co., Ltd. Method and device for universal plug and play communications
US20060056408A1 (en) * 2004-08-28 2006-03-16 Samsung Electronics Co., Ltd. Method and device for universal plug and play communications
US20070297396A1 (en) * 2006-06-22 2007-12-27 Avigdor Eldar Secure and automatic provisioning of computer systems having embedded network devices
US20090238099A1 (en) * 2008-03-24 2009-09-24 Qualcomm Incorporated Dynamic home network assignment
US8503460B2 (en) 2008-03-24 2013-08-06 Qualcomm Incorporated Dynamic home network assignment
US20090254668A1 (en) * 2008-04-03 2009-10-08 Samsung Electronics Co. Ltd. System and method for searching for session id in wireless mobile ip communication system
US8392584B2 (en) * 2008-04-03 2013-03-05 Samsung Electronics Co., Ltd. System and method for searching for session ID in wireless mobile IP communication system
US20110149873A1 (en) * 2008-08-29 2011-06-23 Chunyan Yao Method and foreign agent group for registering to a home agent of a mobile node
WO2010022562A1 (en) * 2008-08-29 2010-03-04 上海贝尔阿尔卡特股份有限公司 A method and foreign agent group for registering to a home agent of a mobile node
US8817715B2 (en) 2008-08-29 2014-08-26 Alcatel Lucent Method and foreign agent group for registering to a home agent of a mobile node
KR101473678B1 (en) 2008-08-29 2014-12-17 알까뗄 루슨트 A method and foreign agent group for registering to a home agent of a mobile node
US20110179189A1 (en) * 2008-12-26 2011-07-21 Canon Kabushiki Kaisha Communication apparatus, method of controlling the same, program, and storage medium

Also Published As

Publication number Publication date Type
US7461169B2 (en) 2008-12-02 grant

Similar Documents

Publication Publication Date Title
Perkins Mobile ip
US7324499B1 (en) Method and system for automatic call monitoring in a wireless network
US6856624B2 (en) Temporary unique private address
US6515974B1 (en) Mobile computer communication scheme supporting moving among networks of different address systems
US7746873B2 (en) Communication processing system, communication processing method, communication terminal, data transfer controller, and program
US7616615B2 (en) Packet forwarding apparatus for connecting mobile terminal to ISP network
US7096273B1 (en) DHCP over mobile IP
US6366561B1 (en) Method and apparatus for providing mobility within a network
US20010012777A1 (en) Mobile communications system and method thereof
US20050138144A1 (en) Providing location-specific services to a mobile node
US6469998B1 (en) Method and apparatus for communicating data packets from an external packet network to a mobile radio station
US20060206597A1 (en) Method of allocating an internet protocol address in a broadband wireless access system
US20040179532A1 (en) Arrangement for traversing an IPv4 network by IPv6 mobile routers
US7152238B1 (en) Enabling mobility for point to point protocol (PPP) users using a node that does not support mobility
US7227863B1 (en) Methods and apparatus for implementing home agent redundancy
Perkins et al. DHCP for mobile networking with TCP/IP
US6992995B2 (en) Telecommunication enhanced mobile IP architecture for intra-domain mobility
US20040246939A1 (en) Transmission of a binding update message indicating a care of address for delivering data packets to a mobile node via a unidirectional interface
US6636498B1 (en) Mobile IP mobile router
US20060268782A1 (en) Providing mobility management protocol information to a mobile terminal for performing handover in a mobile communication system
US20040073642A1 (en) Layering mobile and virtual private networks using dynamic IP address management
US7061887B2 (en) Multiple mobile IP sessions with dynamically allocated home IP address
US6763012B1 (en) Mobile terminal and method of providing a network-to-network connection
US20070189219A1 (en) Internet protocol tunneling on a mobile network
US6992994B2 (en) Methods and systems for a generalized mobility solution using a dynamic tunneling agent

Legal Events

Date Code Title Description
AS Assignment

Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHANDRA, MADHAVI W.;LEUNG, KENT K.;KULKARNI, MILIND M.;AND OTHERS;REEL/FRAME:013512/0634;SIGNING DATES FROM 20021115 TO 20021118

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8