Browse Prior Art Database

Efficient storage of Email and MMS threads in mobile devices

IP.com Disclosure Number: IPCOM000147293D
Original Publication Date: 2007-Mar-08
Included in the Prior Art Database: 2007-Mar-08
Document File: 5 page(s) / 102K

Publishing Venue

Motorola

Related People

Seshadri Raghavan: AUTHOR [+3]

Abstract

This paper presents an efficient mechanism to store threads of conversation in Email or MMS messages by taking advantage of similar and repetitive content that gets conveyed in each of the conversation threads. This approach makes use of this repetitive information to create equivalence parameters in the form of header and body equivalence and use it to have efficient storage of e-mail and MMS messages.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 46% of the total text.

Document Title

Efficient storage of Email and MMS threads in mobile devices

Authors

1.      Seshadri Raghavan

2.      Jagadish Rajasekaran

3.      Gulprit Singh

Abstract

This paper presents an efficient mechanism to store threads of conversation in Email or MMS messages by taking advantage of similar and repetitive content that gets conveyed in each of the conversation threads.

This approach makes use of this repetitive information to create equivalence parameters in the form of header and body equivalence and use it to have efficient storage of e-mail and MMS messages.

Proposal

Key Definitions

Header equivalence: When all headers of two messages are exactly same.

Subject equivalence: When the subject of two messages are exactly same.

Body equivalence: When the body of two messages are exactly same. This can usually be the case when receiving same forwards from multiple places.

Semantic equivalence: If there is a header and body equivalence between the messages then they can be said to be completely equivalent i.e. there is header, subject and body equivalence.

Semantic Containment: Message A is said to be semantic containment of Message B, if A lies fully within content B. All message parts of A are contained in B and B has a few more additional parts.

Approach: This approach establishes a level of equivalence / containment to store redundant information in messages only once and to be accessed by the set of tables thereby quickly generating the target message views saving lots of space.

The higher the degree of containment, the more optimized the storage is. The level of equivalence/containment can be established by following use cases of Semantic equivalent/Contained message threads.

 

Simple Semantic containment/equivalence

a)      Replying onto a received message.

b)      Mailing to group mailing lists or user defined lists.

More complex scenarios of semantic equivalence/containment

a)      Mail discussion originated with the attachment, and attachment was removed somewhere in mid of discussion.

b)      Headers were modified during the discussions, meaning some recipients were added or remove.

c)      Though the content is not getting duplicated in the approach 1, the same set of headers is still getting duplicated eating up the precious space.

d)      User may choose an old mail and reply therefore breaking the sequence of mail chains and breaking the rule of N containing all previous N-1 messages.

Storage Structure of semantic clustered messages:

The efficient storage structure for the semantically clustered messages is explained as below.

  1. Index File: The index file contains a unique ID to identify each message retrieval location and also contain a small cache to establish some basic equivalence so that the incoming message can be validated further with the actual headers and body.
  2. Map File: Map file can be divided into following sections.

i.                     Co...