Browse Prior Art Database

System and Method of Message Thread Compression in a Client-Server Environment

IP.com Disclosure Number: IPCOM000130504D
Publication Date: 2005-Oct-25
Document File: 1 page(s) / 9K

Publishing Venue

The IP.com Prior Art Database

Abstract

Currently, if a user is participating in a long message thread, there is much duplicate information sent between the device and the server. For each message in the thread, there is the potential for the entire thread up to that point to be sent. Sending only the first part of the message reduces the amount of data that typically gets sent, because once the user has some context, there is no need to request more of the message. However, the first chunk of a message sent to the user often includes part of a previous message that is already stored on the user's device, so bandwidth is wasted. Similarly, if the user requests more of the message to obtain more context, data that is already on the device will be sent to the device again. It would be nice to eliminate this duplication in the data that is sent over the air.

This text was extracted from a Microsoft Word document.
This is the abbreviated version, containing approximately 57% of the total text.

MESSAGE THREA COMPRESSION ON THE SERVER

System and Method of Message Thread Compression in a Client-Server Environment

Disclosed Anonymously

Currently, if a user is participating in a long message thread, there is much duplicate information sent between the device and the server. For each message in the thread, there is the potential for the entire thread up to that point to be sent. Sending only the first part of the message reduces the amount of data that typically gets sent, because once the user has some context, there is no need to request more of the message. However, the first chunk of a message sent to the user often includes part of a previous message that is already stored on the user's device, so bandwidth is wasted.  Similarly, if the user requests more of the message to obtain more context, data that is already on the device will be sent to the device again. It would be nice to eliminate this duplication in the data that is sent over the air.

The server already has a good idea of what messages are stored on the device, thanks to the over-the-air email reconciliation functionality. When the server receives a message for a user, it can heuristically determine if this message is a reply to a previous message by scanning the current message for "-----Original Message-----" or a similar string.  If the server determines that the current message is a reply to a previous message, it can extract the text of the previous message from the current message, and then enume...