Arrangement in a router of a mobile network for optimizing use of messages carrying reverse routing headers

• US 7,209,978 B2
• Filed: 12/13/2002
• Issued: 04/24/2007
• Est. Priority Date: 12/13/2002
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Molteni, Marco, Thubert, Pascal, Wetterwald, Patrick, Auerbach, David
• Primary Examiner(s): Maung; Zarni
• Assistant Examiner(s): DAFTUAR, SAKET K
• Application Number:
  US10/318,179
• Publication Number:
  US 20040117339A1
• Time in Patent Office: 1,593 Days
• Field of Search: 709/242, 707/1
• US Class Current: 709/242
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/36 Backward learning
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/167 Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 translation of Internet protocol [IP] addresses H04L61/2503
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 40/246 Connectivity information discovery
• CPC Class Codes: H04W 40/30 for proactive routing
• CPC Class Codes: H04W 40/32 for defining a routing cluster membership
• CPC Class Codes: H04W 8/082 for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]
• CPC Class Codes: H04W 84/005 Moving wireless networks
• CPC Class Codes: Y10S 707/99931 Database or file accessing

Abstract

A mobile router is configured for optimized utilization of reverse routing headers, to specify a path between an originating mobile router and a home agent. Reverse routing headers enable each mobile router within the path to the home agent to specify its care of address, enabling the home agent to establish a bidirectional tunnel to the originating mobile router via the corresponding mobile router. The mobile router selectively updates the reverse routing header in a received packet by inserting the source address value of the received packet into the reverse routing header and inserting its corresponding care of address into the source address field, based on whether the mobile router lacks a routing table entry that specifies reachability of a most recent entry in the reverse routing header via the source address value. The mobile router also may request the originating mobile router to increase the reverse routing header size.

Claims

1. A method in a mobile router of a mobile network, the method including:

receiving a packet having a source address field with a source address value specifying a source of the packet, a destination address field with a destination address value specifying a home agent for an originating mobile router, and a reverse routing header configured for storing addresses, the reverse routing header having at least a first entry that specifies a care of address for the originating mobile router;

selectively updating the reverse routing header by inserting the source address value into a detected empty entry field of the reverse routing header, based on a determined absence of a routing table entry that specifies reachability of an identified entry within the reverse routing header via the source address value; and

outputting the packet to an identified router, including inserting a care of address for the mobile router into the source address field.

2. The method of claim 1, further including sending to the originating mobile router a message requesting increasing the size of the reverse routing header based on a determined absence of the empty entry field.

3. The method of claim 2, wherein the sending includes generating an IPv6 header for the message that specifies a path to the originating mobile router based on the reverse routing header.

4. The method of claim 3, wherein the sending includes sending the message according to Internet Control Message Protocol (ICMP).

5. The method of claim 1, wherein the outputting includes outputting the packet, having the reverse routing header without having been updated by the mobile router, based on the determined presence of the routing table entry.

6. The method of claim 1, further including:

detecting a second routing table entry that specifies reachability of the identified entry within the reverse routing header via a second address distinct from the source address value; and

invalidating the second routing table entry as obsolete based on the detecting of the second address distinct from the source address value.

7. A method in a mobile router, the method including:

attaching to a default router based on a corresponding received router advertisement message having a tree information option field having attributes specifying a network topology model of the corresponding router;

generating an IPv6 based reverse routing header having a home address field specifying a corresponding prescribed home address for the mobile router identifiable by a prescribed home agent, and a selected number of empty address slots enabling storage of respective care-of addresses of routers between the mobile router and the prescribed home agent, the selected number determined at least based on the network topology model;

second generating an outer IPv6 header having a source address field specifying the care-of address of the mobile router and a destination address field specifying an address of the prescribed home agent; and

outputting a packet, including at least the outer IPv6 header and selectively including the IPv6 based reverse routing header, to the default router.

8. The method of claim 7, wherein the generating step includes selecting the selected number based on a tree depth field, specified as one of the attributes of the network topology model, that specifies a number of routers in a path between the mobile router and top level mobile router.

9. The method of claim 8, further including:

third generating a truncated IPv6 based routing header having the home address field and none of the address slots for the storage of the respective care-of addresses of the routers between the mobile router and the prescribed home agent; and

outputting another packet, including a selected one of the IPV6 based reverse routing header and the truncated IPv6 based routing header, based on a determined stability of the network topology model.

10. The method of claim 9, wherein the determined stability is based on expiration of an inactivity timer.

11. The method of claim 8, further comprising:

receiving an Internet Control Message Protocol (ICMP) message specifying an insufficient number of the empty address slots;

the selecting including increasing the selected number based on the ICMP message.

12. The method of claim 8, further comprising:

receiving a message from the home agent having a routing header specifying the respective care of addresses for the routers between the mobile router and the prescribed home agent;

the selecting including determining the selected number based on the routing header.

13. A mobile router configured for establishing communications within a mobile network, the mobile router including:

an IPv6 interface configured for receiving a packet having a source address field with a source address value specifying a source of the packet, a destination address field with a destination address value specifying a home agent for an originating mobile router, and a reverse routing header configured for storing addresses, the reverse routing header having at least a first entry that specifies a care of address for the originating mobile router; and

a routing resource configured for selectively updating the reverse routing header by inserting the source address value into a detected empty entry field of the reverse routing header, based on a determined absence of a routing table entry that specifies reachability of an identified entry within the reverse routing header via the source address value;

the IPv6 interface configured for outputting the packet to an identified router the packet including a care of address for the mobile router having been inserted by the mobile router into the source address field.

14. The mobile router of claim 13, wherein the routing resource is configured for generating for transmission to the originating mobile router a message requesting increasing the size of the reverse routing header based on a determined absence of the empty entry field.

15. The mobile router of claim 14, wherein the routing resource is configured for generating an IPv6 header for the message that specifies a path to the originating mobile router based on the reverse routing header.

16. The mobile router of claim 15, wherein the routing resource is configured for generating the message according to Internet Control Message Protocol (ICMP).

17. The mobile router of claim 13, wherein the routing resource is configured for generating the packet, having the reverse routing header without having been updated, based on the determined presence of the routing table entry.

18. The mobile router of claim 13, wherein the routing resource is configured for:

detecting a second routing table entry that specifies reachability of the identified entry within the reverse routing header via a second address distinct from the source address value; and

invalidating the second routing table entry as obsolete based on the detecting of the second address distinct from the source address value.

19. A mobile router configured for establishing communications within a mobile network, the mobile router including:

a routing resource configured for;

(1) attaching to a default router based on a corresponding received router advertisement message having a tree information option field having attributes specifying a network topology model of the corresponding router,

(2) generating an IPv6 based reverse routing header having a home address field specifying a corresponding prescribed home address for the mobile router identifiable by a prescribed home agent, and a selected number of empty address slots enabling storage of respective care-of addresses of routers between the mobile router and the prescribed home agent, the selected number determined at least based on the network topology model, and

(3) second generating an outer IPv6 header having a source address field specifying the care-of address of the mobile router and a destination address field specifying an address of the prescribed home agent; and

an IPv6 interface configured for outputting to the default router a packet including at least the outer IPv6 header, the routing resource having selectively added the IPv6 based reverse routing header to the packet.

20. The mobile router of claim 19, wherein the routing resource is configured for selecting the selected number based on a tree depth field, specified as one of the attributes of the network topology model, that specifies a number of routers in a path between the mobile router and top level mobile router.

21. The mobile router of claim 20, wherein the routing resource further is configured for:

third generating a truncated IPv6 based routing header having the home address field and none of the address slots for the storage of the respective care-of addresses of the routers between the mobile router and the prescribed home agent; and

selecting one of the IPv6 based reverse routing header and the truncated IPv6 based routing header for the packet, based on a determined stability of the network topology model.

22. The mobile router of claim 21, wherein the determined stability is based on expiration of an inactivity timer.

23. The mobile router of claim 20, wherein the routing resource, in response to receiving an Internet Control Message Protocol (ICMP) message specifying an insufficient number of the empty address slots, is configured for increasing the selected number based on the ICMP message.

24. The mobile router of claim 20, wherein the routing resource is configured for receiving a message from the home agent having a routing header specifying the respective care of addresses for the routers between the mobile router and the prescribed home agent, the routing resource configured for determining the selected number based on the routing header.

25. A mobile router configured for establishing communications within a mobile network, the mobile router including:

means for receiving a packet having a source address field with a source address value specifying a source of the packet, a destination address field with a destination address value specifying a home agent for an originating mobile router, and a reverse routing header configured for storing addresses, the reverse routing header having at least a first entry that specifies a care of address for the originating mobile router; and

means for selectively updating the reverse routing header by inserting the source address value into a detected empty entry field of the reverse routing header, based on a determined absence of a routing table entry that specifies reachability of an identified entry within the reverse routing header via the source address value;

the means for receiving configured for outputting the packet to an identified router, the packet including a care of address for the mobile router having been inserted by the mobile router into the source address field.

26. The mobile router of claim 25, wherein the means for selectively updating is configured for generating for transmission to the originating mobile router a message requesting increasing the size of the reverse routing header based on a determined absence of the empty entry field.

27. The mobile router of claim 26, wherein the means for selectively updating is configured for generating an IPv6 header for the message that specifies a path to the originating mobile router based on the reverse routing header.

28. The mobile router of claim 27, wherein the means for selectively updating is configured for generating the message according to Internet Control Message Protocol (ICMP).

29. The mobile router of claim 25, wherein the means for selectively updating is configured for generating the packet, having the reverse routing header without having been updated, based on the determined presence of the routing table entry.

30. The mobile router of claim 25, wherein the means for selectively updating is configured for:

detecting a second routing table entry that specifies reachability of the identified entry within the reverse routing header via a second address distinct from the source address value; and

invalidating the second routing table entry as obsolete based on the detecting of the second address distinct from the source address value.

31. A mobile router configured for establishing communications within a mobile network, the mobile router including:

means for attaching to a default router based on a corresponding received router advertisement message having a tree information option field having attributes specifying a network topology model of the corresponding router,

the means for attaching further configured for generating an IPv6 based reverse routing header having a home address field specifying a corresponding prescribed home address for the mobile router identifiable by a prescribed home agent, and a selected number of empty address slots enabling storage of respective care-of addresses of routers between the mobile router and the prescribed home agent, the selected number determined at least based on the network topology model,

the means for attaching further configured for second generating an outer IPv6 header having a source address field specifying the care-of address of the mobile router and a destination address field specifying an address of the prescribed home agent; and

means for outputting to the default router a packet including at least the outer IPv6 header, the means for attaching having selectively added the IPv6 based reverse routing header to the packet.

32. The mobile router of claim 31, wherein the means for attaching is configured for selecting the selected number based on a tree depth field, specified as one of the attributes of the network topology model, that specifies a number of routers in a path between the mobile router and top level mobile router.

33. The mobile router of claim 32, wherein the means for attaching further is configured for:

third generating a truncated IPv6 based routing header having the home address field and none of the address slots for the storage of the respective care-of addresses of the routers between the mobile router and the prescribed home agent; and

selecting one of the IPv6 based reverse routing header and the truncated IPv6 based routing header for the packet, based on a determined stability of the network topology model.

34. The mobile router of claim 33, wherein the determined stability is based on expiration of an inactivity timer.

35. The mobile router of claim 32, wherein the means for attaching, in response to receiving an Internet Control Message Protocol (ICMP) message specifying an insufficient number of the empty address slots, is configured for increasing the selected number based on the ICMP message.

36. The mobile router of claim 32, wherein the means for attaching is configured for receiving a message from the home agent having a routing header specifying the respective care of addresses for the routers between the mobile router and the prescribed home agent, the means for attaching configured for determining the selected number based on the routing header.