Header compression in messages

• US 7,398,325 B2
• Filed: 09/04/2003
• Issued: 07/08/2008
• 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): Burgess; Glenton B.
• Assistant Examiner(s): Higa; Brendan Y
• Application Number:
  US10/656,946
• Publication Number:
  US 20050055464A1
• Time in Patent Office: 1,769 Days
• Field of Search: 709246-247, 709/230, 709/232, 709/233, 709/236, 370471-477
• 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 first data processing system, said method comprising:

receiving, from a second data processing system, a message including a compressed header comprising an identifier to a referenced, uncompressed header and changes from said referenced, uncompressed header, and in response,

determining impact of header compression on performance, and

if favorable, supporting the header compression for subsequent communications, and

if unfavorable, refusing to support the header compression for the subsequent communications, wherein if the impact of header compression on performance is determined to be favorable, then handling said message by forming another uncompressed header based on said referenced, uncompressed header and said changes, and returning another identifier for said another uncompressed header to the second data processing system, said another identifier being assigned by the first data processing system for use in another compressed header generated by the second data processing system.

2. A method for compressing message headers by a first data processing system, said method comprising:

receiving, from a second data processing system, a message including a compressed header, wherein said compressed header includes an identifier to a referenced header and changes relative to said referenced header;

determining impact of header compression on performance, and

if favorable, handling said message, and

if unfavorable, refusing to handle said message,

wherein if the impact of header compression on performance is favorable, further comprising reconstructing said message with an uncompressed header based on said referenced header and said changes, before the step of handling said message, and returning another identifier for said uncompressed header to the second data processing system, said another identifier being assigned by the first data processing system for use in another compressed header generated by the second data processing system.

3. A method for compressing message headers by a first data processing system, said method comprising:

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

determining if there is sufficient storage available to support the header compression, and

if so, supporting the header compression for subsequent communications, and

if not, refusing to support the header compression for the subsequent communications,

wherein said compressed header includes an identifier to a referenced, uncompressed header and changes relative to said referenced, uncompressed header, and the receiving step comprises receiving the message including a compressed header, and if there is the sufficient storage available to support the header compression, then generating another uncompressed header based on said referenced, uncompressed header and said changes and returning another identifier for said generated another uncompressed header to the second data processing system to be used for a subsequent compressed header, said another identifier being assigned by the first data processing system.