Browse Prior Art Database

Enhanced Email Communication with Index Enabled

IP.com Disclosure Number: IPCOM000235960D
Publication Date: 2014-Apr-01
Document File: 4 page(s) / 163K

Publishing Venue

The IP.com Prior Art Database

Abstract

In this article we present a way to bind the email body with an index and illustrate how to use this index in the mail sending/receiving process to replace the email body. and how it works from email sender and receiver perspective. In this way we can reduce the network traffic, save the storage in both email server and client sides and improve email send/receive response time.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 49% of the total text.

Page 01 of 4

Enhanced Email Communication with Index Enabled

Email is a very common concept and almost everybody has his/her own email box if he/she has any experience using computer with network connection. People are using emails to send messages as well as attach some additional files in one email. Also it is very likely that someone sends one email to a couple of relative people, and all the relative people will probably reply the email to the same amount of people, or forward that original email to others that he/she think the others should also read the original email get their feedback or response. There are too many email communication happened everyday and many of emails are copied or forwarded many times (with same email subject but add "Re:" or "Fw:" to indicate whether it is a replied or forwarded email).

When reply or forward an email, in most cases the email history will be included in the replied or forwarded email body to help the receiver have a good context to understand the whole email more clearly without losing any important information. Keeping email history in each email is a good habit, but it will definitely increase the email size and bring many corresponding disadvantages :

1. Increase the network traffic;

2. Occupy more storage in both email server and client;

3. Huge number of emails with same email subject, and most probably the latest one will have all the content of old ones. User need to read all such emails (with same subject) manually and remove the deprecated ones from their email box to release the storage.

4. It is very likely there are attachments in original email, but the attachments were deleted during the reply or forward happened. In this case, just keep the latest version of email will probably lose all such attachments which is really not user expected. It is very difficult and boring to ask the user to maintain all such attachments in the latest email , but it is also not recommended to keep the attachments in every replied or forwarded email without deleting them with email history included .

Considering the emails are growing bigger and bigger when they were replied or forwarded, and all the troubles it brings to each email user, here is the core innovation ideas which were based on using email indexes to resolve above issues.

1. Generate an index to identify each unique email 2. Storing the identical index in email tags (if doesn't exist, then create new tags)

3. Instead of including all the history email content in the newly replied or forwarded emails , replacing each email object (email body) with corresponding email index when sending the email to a couple of receivers following below approaches
a. For those receivers who already received subset of whole email chain, only replace all the subset emails with their

corresponding index.

b. For those receivers who have never received any subset of the whole email chain, send the whole email chain without

replacing any emails with any indexes.

4....