Header compression in messages

• US 7,594,036 B2
• Filed: 08/30/2007
• Issued: 09/22/2009
• Est. Priority Date: 09/04/2003
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Weller, Scott W.
• Primary Examiner(s): Etienne; Ario
• Assistant Examiner(s): Higa; Brendan Y
• Application Number:
  US11/847,617
• Publication Number:
  US 20070299988A1
• Time in Patent Office: 754 Days
• Field of Search: 709246-247, 709/230, 709/232, 709/233, 709/236, 711/100, 711/154
• US Class Current: 709/247
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC

Abstract

Compression of message headers. A message including an uncompressed header, a message including a compressed header or a request to support header compression is received. In response, a determination of the impact of header compression on performance is determined. If the determination is favorable, then header compression is supported for subsequent communications. However, if the determination is not favorable, then header compression is not supported for subsequent communications. If the impact of header compression on performance is determined to be favorable, then an identifier for a reference header is returned. The identifier is for use in a subsequent compressed header. The subsequent compressed header comprises the identifier and changes relative to the reference header. A server receives a message including a compressed header. The server determines whether it has sufficient memory or storage to support header compression. If so, the server handles the message, but if not, the server refuses to handle the message or notifies a sender of the message that it will not support header compression for subsequent messages.

Claims

1. A method for processing message headers by a data processing system, said method comprising the steps of:

receiving a message from a second data processing system, the message including an uncompressed header, a compressed header or a request to support header compression, and in response,

determining if there is sufficient storage available at the data processing system to support header compression, and

if so, supporting header compression for subsequent communications and returning an identifier to the second data processing system, wherein said identifier that is returned to the second data processing system is useable by the second data processing system in subsequent messages sent by the second data processing system to identify the uncompressed header maintained by the data processing system in lieu of the second data processing system sending header information to the data processing system.

2. A method as set forth in claim 1 wherein the receiving step comprises the step of receiving the message including the uncompressed header.

3. A method as set forth in claim 1,

wherein said compressed header includes (i) an identifier previously returned to the second data processing system by the data processing system which identifies a referenced, uncompressed header maintained by the data processing system and (ii) changes relative to said referenced header, and the receiving step comprises the step of receiving the message including the compressed header, and if there is sufficient storage available to support header compression, then generating another uncompressed header based on said referenced header and said changes.

4. A method as set forth in claim 3 further comprising the steps of handling said message and returning another identifier to the second data processing system for said generated another uncompressed header.