METHODS FOR OPTIMIZED TUNNEL HEADERS IN A MOBILE NETWORK

• US 20080101366A1
• Filed: 10/31/2006
• Published: 05/01/2008
• Est. Priority Date: 10/31/2006
• Status: Abandoned Application

• Current Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: VENKITARAMAN, NARAYANAN, NARAYANAN, VIDYA
• Application Number:
  US11/555,019
• Publication Number:
  US 20080101366A1
• Time in Patent Office: Days
• US Class Current: 370/392
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• 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: H04W 28/06 Optimizing the usage of the radio link, e.g. header compression, information sizing , discarding information system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365
• 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]

Abstract

A sending device replace an original Internet Protocol (IP) header in a packet with a shim that includes some information copied from the IP header, such that the resultant packet being sent from a source device to a destination device has a shim that is smaller in byte size than the header that it replaces. The receiving device copies some different information from the original header into another header. The sending device can further optimize the packet by: eliminating an IP header associated with a security protocol; eliminating a mobility tunnel for a node behind a mobile router (MR); and selective use of a security tunnel for the MR. A receiving device, upon receiving the optimized packet, restores the original IP header using the information in the shim (and other header(s)) and restores any other headers that were removed prior to forwarding the packet toward its intended destination.

Claims

1. A method for header optimization comprising the steps of:

receiving a first message comprising data and a first header having a first size, the first header including information to enable transporting of the first message from a source device to a destination device;

generating a first shim having a second size that is smaller than the first size, the shim comprising a first portion of the information in the first header;

generating at least a second header comprising a second portion of the information in the first header;

generating a second message comprising the data, the first shim and the at least a second header; and

forwarding the second message toward the destination device.

2. The method of claim 1, wherein the first portion of the information comprises at least one of a first Internet Protocol (IP) address for the destination device and a second IP address for the source device.

3. The method of claim 1, wherein the at least a second header comprises at least one of a security protocol header, a first Internet Protocol (IP) header associated with the security protocol header and a first mobility header.

4. The method of claim 3, wherein the at least a second header comprises the security protocol header and the first IP header and wherein the second portion of the information comprises at least one of next header information, identification and fragmentation fields, Type of Service field and Time to Live field from the first IP header.

5. The method of claim 4, wherein the security protocol header comprises an IPSec ESP header.

6. The method of claim 5 further comprising the step of encrypting the data and the first shim and performing an authentication protocol on the ESP header and encrypted data and first shim, wherein the authentication protocol is performed using at least some of the information in the first header to enable the recreation of the first header in a second node.

7. The method of claim 1 further comprising the step of indicating in the second message at least the presence of the first shim.

8. The method of claim 5 further comprising the step of using bits in a Security Parameter Index field of the ESP header for indicating presence of at least one of:

the first shim and a type of the first shim;

a More Fragments field in the first header; and

IP options in the first header.

9. The method of claim 3, wherein the at least a second header comprises the security protocol header and the first mobility header and wherein the second portion of the information comprises at least one of next header information, identification and fragmentation fields, Type of Service field and Time to Live field from the first IP header.

10. The method of claim 9 further comprising the steps of:

generating the first IP header with at least some of the second portion of the information;

generating the first mobility header; and

copying the at least some of the second portion of the information from the first IP header to the first mobility header.

11. The method of claim 1 further comprising the steps of:

determining whether the first message includes a security protocol header;

if the first message includes a security protocol header, copying at least some of the second potion of the information into the security protocol header to generate the at least a second header; and

if the first message does not include a security protocol header, creating a security protocol header and copying at least some of the second potion of the information into the created security protocol header to generate the at least a second header.

12. The method of claim 1 further comprising the steps of:

detecting a level of traffic between the source and destination device that exceeds a threshold level;

generating an index that is representative of the source and destination device pair instead of generating the first shim, wherein the index has a third size that is smaller than the second size; and

embedding the index in the second message, wherein the second message comprises the data, the at least a second header and the index.

13. A method for header optimization comprising the steps of:

receiving a first message comprising data and at least a first header;

determining that the first message further comprises a first shim having a first size and including a first portion of information from a second header having a second size that is larger than the first size, the second header being included in a second message and the information from the second header to enable transporting of the second message from a source device to a destination device, wherein the at least a first header includes a second portion of the information from the second header;

recreating the second header using the first and second portions of information;

generating a third message using the data and the recreated second header; and

forwarding the third message toward the destination device.

14. The method of claim 13 further comprising the steps of:

obtaining state information associated with a first node connected to a mobile network behind a mobile node;

detecting that at least a third header was removed from the first message prior to the first message being sent; and

recreating, in one of the mobile node and a mobility agent, the third header using the state information, wherein the third message is generated further using the recreated third header.

15. The method of claim 14, wherein the at least a first header comprises a security protocol header and a mobility header for the mobile node and wherein the at least a third header comprises at least one of:

an Internet Protocol (IP) header associated with the security protocol header; and

a mobility header for the first node.

16. Apparatus for header optimization comprising:

a first interface receiving a first message comprising data and a first header having a first size, the first header including information to enable transporting of the first message from a source device to a destination device;

a processing device coupled to the first interface and;

generating a first shim having a second size that is smaller than the first size, the shim comprising a first portion of the information in the first header;

generating at least a second header comprising a second portion of the information in the first header; and

generating a second message comprising the data, the first shim and the at least a second header; and

a second interface coupled to the processing device and forwarding the second message toward the destination device.

17. The apparatus of claim 16, wherein:

the first interface further receiving a third message comprising second data and at least a third header;

the processing device further;

determining that the third message further comprises a second shim having a third size and including a first portion of information from a fourth header having a fourth size that is larger than the third size, the fourth header being included in a fourth message and the information from the fourth header to enable transporting of the fourth message from a second source device to a second destination device, wherein the at least a third header includes a second portion of the information from the fourth header;

recreating the fourth header using the first and second portions of information from the fourth header; and

generating a fifth message using the second data and the recreated fourth header; and

the second interface further forwarding the fifth message toward the destination device.

18. The apparatus of claim 16, wherein the first and second interfaces are one of wireless and wired.

19. The apparatus of claim 16, wherein the apparatus comprises at least one of:

a mobile router, a mobile host, a home agent, a foreign agent and a virtual private network server.

20. The apparatus of claim 16, wherein the apparatus operates in accordance with at least one of:

Internet Protocol version 4 (IPv4), IPv6, Mobile IP for IPv4, Mobile IP for IPv6 and IP Security Protocol.