# US 2003/0217145 A1 · Method and apparatus for reusing DHCP addresses in home addresses of mobile IP clients

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0217145 A1
- Document ID: US20030217145A1
- Status: Published application
- Kind: A1
- Application number: 10/241,969
- Filed: 2002-09-11
- Published: 2003-11-20
- Earliest claimed: 2002-03-05
- Assignees: Cisco Technology, Inc.
- Inventors: Kent K. Leung; Milind M. Kulkarni; Alpesh Patel
- Web page: https://patentgrep.com/patent/US20030217145A1

## CPC

- H04W 8/04: Registration at HLR or HSS [Home Subscriber Server]
- H04L 61/5014: using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
- H04L 61/5053: Lease time; Renewal aspects
- H04W 8/26: Network addressing or numbering for mobility support
- H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W 80/04: Network layer protocols, e.g. mobile IP [Internet Protocol]
- H04W 88/18: Service support devices; Network management devices
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods and apparatuses for conserving addresses. The invention allows a mobile node to manage its own address, shifting responsibility away from the home agent. The home agent is able to detect when a mobile node has already been assigned an address for use of resources on the network. When the home agent recognizes that the mobile address has already been assigned an address, it allows the mobile node to use its already-assigned address in connection with mobile IP services. Additionally, the mobile node can be notified that it is now responsible for renewing the address.

## Claims

### Claim 1

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 from a DHCP server, the request being received from a Mobile Node;
routing the request for assignment of the DHCP address to the DHCP server;
receiving a registration request from the mobile node, the registration request requesting assignment of a home address to the mobile node; and
sending a registration reply to the mobile node, the registration reply indicating that the mobile node is to use the DHCP address as the home address.

### Claim 2 (depends on 1)

The method as recited in claim 1, further comprising;
receiving the DHCP address from the DHCP server; and
providing the DHCP address received from the DHCP server to the mobile node.

### Claim 3 (depends on 2)

The method as recited in claim 2, further comprising:
receiving a lease time associated with the DHCP address from the DHCP server; and
providing the lease time associated with the DHCP server to the mobile node.

### Claim 4 (depends on 3)

The method as recited in claim 3, wherein the registration reply indicates that the mobile node is to manage the DHCP address and the lease time associated with the DHCP address.

### Claim 5 (depends on 1)

The method as recited in claim 1, further comprising:
processing the registration request such that a binding is maintained between the mobile node and the DHCP address.

### Claim 6 (depends on 1)

The method as recited in claim 1, wherein the registration reply indicates that the mobile node is to manage the DHCP address and associated lease time.

### Claim 7 (depends on 1)

The method as recited in claim 1, further comprising:
determining whether the mobile node and the home agent are in the same domain;
wherein sending the registration reply indicating that the mobile node is to use the DHCP address as the home address is performed when it has been determined that the mobile node and the home agent are in the same domain.

### Claim 8 (depends on 1)

The method as recited in claim 1, further comprising:
obtaining the DHCP address from the registration request; and
setting the home address field of the registration reply to the DHCP address.

### Claim 9 (depends on 1)

The method as recited in claim 1, further comprising:
maintaining a mapping between the DHCP address and a link-layer address associated with the mobile node.

### Claim 10

A method of conserving addresses comprising:
receiving a request for assignment of a first address;
routing the request for assignment to a server that can satisfy the request;
receiving a request for assignment of a second address;
recognizing that the request for assignment of the first address and the request for assignment of the second address came from a single device; and
alerting the single device to use a single address to satisfy both requests.

### Claim 11 (depends on 10)

The method of claim 10, wherein the first address is to be used by the single device to facilitate the single device's use of network resources.

### Claim 12 (depends on 10)

The method of claim 10, wherein the second address is to be used by the single device to facilitate the single device's ability to maintain connectivity while roaming.

### Claim 13 (depends on 10)

The method of claim 10, wherein recognizing is accomplished by analyzing an extension accompanying the request for assignment of the second address.

### Claim 14 (depends on 13)

The method of claim 13, wherein the extension is a GNAIE.

### Claim 15 (depends on 10)

The method of claim 10, wherein recognizing is accomplished by analyzing the source of the request for assignment of the second address.

### Claim 16 (depends on 10)

The method of claim 10, further comprising storing information relating to the request for assignment of the first address.

### Claim 17 (depends on 16)

The method of claim 16, wherein recognizing is accomplished by comparing information relating to the request for assignment of the second address with the stored information.

### Claim 18 (depends on 10)

The method of claim 10, further comprising sending a registration reply to the single device in response to the request for assignment of the second address.

### Claim 19 (depends on 18)

The method of claim 18, wherein alerting is accomplished by appending an extension to the registration reply.

### Claim 20 (depends on 18)

The method of claim 18, wherein alerting is accomplished by assigning the single address to the second address in the registration reply and allowing the single device to compare the assigned first address with the assigned second address.

### Claim 21 (depends on 18)

The method of claim 18, wherein alerting is accomplished by setting the home address field of the registration reply to the single address, wherein the second address is the home address.

### Claim 22 (depends on 20)

The method as recited in claim 20, wherein the single address is the first address.

### Claim 23 (depends on 22)

The method as recited in claim 22, wherein the first address is an address assigned by a DHCP server.

### Claim 24 (depends on 10)

The method of claim 10, wherein the single device initiates its own renewal procedures.

### Claim 25

A mobile IP network device 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 request for assignment of a first address;
routing the request for assignment to a server that can satisfy the request;
receiving a request for assignment of a second address;
recognizing that the request for assignment of the first address and the request for assignment of the second address came from a single device; and
alerting the single device to use a single address to satisfy both requests.

### Claim 26 (depends on 25)

The mobile IP network device of claim 25, wherein the first address is to be used by the single device to facilitate the single device's use of network resources.

### Claim 27 (depends on 25)

The mobile IP network device of claim 25, wherein the second address is to be used by the single device to facilitate the single device's ability to maintain connectivity while roaming.

### Claim 28 (depends on 25)

The mobile IP network device of claim 25, wherein recognizing is accomplished by analyzing an extension accompanying the request for assignment of the second address.

### Claim 29 (depends on 28)

The mobile IP network device of claim 28, wherein the extension is a GNAIE.

### Claim 30 (depends on 25)

The mobile IP network device of claim 25, wherein recognizing is accomplished by analyzing the source of the request for assignment of the second address.

### Claim 31 (depends on 25)

The mobile IP network device of claim 25, wherein the processor is operable to further perform instructions that include storing information relating to the request for assignment of the first address.

### Claim 32 (depends on 31)

The mobile IP network device of claim 31, wherein recognizing is accomplished by comparing information relating to the request for assignment of the second address with the stored information.

### Claim 32 (depends on 25)

The mobile IP network device of claim 25, wherein the processor is operable to further perform instructions that include sending a registration reply to the single device in response to the request for assignment of the second address.

### Claim 33 (depends on 32)

The mobile IP network device of claim 32, wherein alerting is accomplished by appending an extension to the registration reply.

### Claim 34 (depends on 32)

The mobile IP network device of claim 32, wherein alerting is accomplished by assigning the single address to the second address in the registration reply and allowing the single device to compare the assigned first address with the assigned second address.

### Claim 35 (depends on 32)

The mobile IP network device of claim 32, wherein alerting is accomplished by setting the home address field of the registration reply to the single address, wherein the second address is the home address.

### Claim 36 (depends on 34)

The method as recited in claim 34, wherein the single address is the first address.

### Claim 37 (depends on 36)

The method as recited in claim 36, wherein the first address is an address assigned by a DHCP server.

### Claim 38 (depends on 25)

The mobile IP network device of claim 25, wherein the single device initiates its own renewal procedures.

### Claim 39

A computer program product comprising:
a computer usable medium having computer readable code embodied therein, the computer readable code including computer code for
requesting assignment of a first address, the first address to be used to facilitate a mobile node's use of network resources;
requesting assignment of a second address, the second address to be used to facilitate the mobile node's ability to maintain connectivity while roaming; and
using a single address as both the first address and the second address.

### Claim 40 (depends on 39)

The computer program product of claim 39, wherein the first address is to be used by the single device to facilitate the single device's use of network resources.

### Claim 41 (depends on 39)

The computer program product of claim 39, wherein the second address is to be used by the single device to facilitate the single device's ability to maintain connectivity while roaming.

### Claim 42 (depends on 39)

The computer program product of claim 39, wherein recognizing is accomplished by analyzing an extension accompanying the request for assignment of the second address.

### Claim 43 (depends on 42)

The computer program product of claim 42, wherein the extension is a GNAIE.

### Claim 44 (depends on 39)

The computer program product of claim 39, wherein recognizing is accomplished by analyzing the source of the request for assignment of the second address.

### Claim 45 (depends on 39)

The computer program product of claim 39, wherein the computer readable code includes computer code for storing information relating to the request for assignment of the first address.

### Claim 46 (depends on 45)

The computer program product of claim 45, wherein recognizing is accomplished by comparing information relating to the request for assignment of the second address with the stored information.

### Claim 47 (depends on 39)

The computer program product of claim 39, wherein the computer readable code includes computer code for sending a registration reply to the single device in response to the request for assignment of the second address.

### Claim 48 (depends on 47)

The computer program product of claim 47, wherein alerting is accomplished by appending an extension to the registration reply.

### Claim 49 (depends on 47)

The computer program product of claim 47, wherein alerting is accomplished by assigning the single address to the second address in the registration reply and allowing the single device to compare the assigned first address with the assigned second address.

### Claim 50 (depends on 47)

The computer program product of claim 47, wherein alerting is accomplished by setting the home address field of the registration reply to the single address, wherein the second address is the home address.

### Claim 51 (depends on 49)

The method as recited in claim 49, wherein the single address is the first address.

### Claim 52 (depends on 51)

The method as recited in claim 51, wherein the first address is an address assigned by a DHCP server.

### Claim 53 (depends on 39)

The computer program product of claim 39, wherein the single device initiates its own renewal procedures.

### Claim 54

A home agent comprising:
means for receiving a request for assignment of a first address;
means for routing the request for assignment to a server that can satisfy the request;
means for receiving a request for assignment of a second address;
means for recognizing that the request for assignment of the first address and the request for assignment of the second address came from a single device; and
means for alerting the single device to use a single address to satisfy both requests.

### Claim 55

A method of conserving addresses comprising:
requesting assignment of a first address, the first address to be used to facilitate a mobile node's use of network resources;
requesting assignment of a second address, the second address to be used to facilitate the mobile node's ability to maintain connectivity while roaming; and
using a single address as both the first address and the second address.

### Claim 56

A mobile node comprising:
means for requesting assignment of a first address, the first address to be used to facilitate a mobile node's use of network resources; and
means for requesting assignment of a second address, the second address to be used to facilitate the mobile node's ability to maintain connectivity while roaming;
wherein a single address is used as both the first address and the second address.

### Claim 57

A mobile IP network device 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 requesting assignment of a first address, the first address to be used to facilitate a mobile node's use of network resources; requesting assignment of a second address, the second address to be used to facilitate the mobile node's ability to maintain connectivity while roaming; and
using a single address as both the first address and the second address.

### Claim 58

A computer program product comprising:
a computer usable medium having computer readable code embodied therein, the computer readable code including computer code for
requesting assignment of a first address, the first address to be used to facilitate a mobile node's use of network resources;
requesting assignment of a second address, the second address to be used to facilitate the mobile node's ability to maintain connectivity while roaming; and
using a single address as both the first address and the second address.

### Claim 59 (depends on 58)

The computer program product of claim 58, wherein requesting assignment of the first address is performed in the context of a DHCPDISCOVER message.

### Claim 60 (depends on 59)

The computer program product of claim 59, wherein the single address is received in a DHCPACK message.

### Claim 61 (depends on 58)

The computer program product of claim 58, wherein requesting assignment of the second address is performed in the context of a Mobile IP registration request.

### Claim 62 (depends on 58)

The computer program product of claim 58, wherein the computer readable code includes computer code for:
receiving a registration response in response to requesting assignment of the second address; and
recognizing that the single address must be managed by the mobile node.

### Claim 63 (depends on 62)

The computer program product of claim 62, wherein recognizing is accomplished by interpreting an extension to the registration reply.

### Claim 63 (depends on 62)

The computer program product of claim 62, wherein recognizing is accomplished by determining that the first address is the same as the second address.

### Claim 64 (depends on 58)

The computer program product of claim 58, wherein the computer readable code includes computer code for managing the single address.

### Claim 65 (depends on 58)

The computer program product of claim 58, wherein the computer readable code includes computer code for requesting that the mobility bindings be refreshed.

### Claim 66 (depends on 58)

The computer program product of claim 58, wherein the device is used in a Mobile IP environment.
