Mobile Email Sent File Synchronization and Resend Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing email systems with mobile wireless communication devices often fail to synchronize 'messages sent' files effectively between devices and servers, leading to redundant data transmission and waste of network bandwidth and device battery, as they typically require sending the entire message content for resending, even when the server already has the message.
Innovation Solution
Implementing a protocol that sends only an abbreviated reference ID for resending messages, allowing the server to retrieve and resend the original message if available, and requesting the entire message only if the ID is unknown, thus reducing data transmission and conserving bandwidth and battery life.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire message content is sent for resending, then the server can ensure message availability, but network bandwidth and device battery are wasted
Solution Approach 1:
The patent extracts only the essential message identification elements (message ID, subject, date) from the complete message content to create a compact representation. This extracted information is sufficient for the server to identify and retrieve the full message, eliminating the need to transmit redundant data while ensuring message availability.
Solution Approach 2:
Instead of copying and transmitting the entire message content, the system creates a lightweight reference copy containing only identifying elements. The server uses this reference to locate the original message in its storage, effectively copying only the necessary identification data rather than the full message body.
2Productivity
If the mobile device maintains synchronized sent message files, then message resending can be optimized, but synchronization complexity increases
Solution Approach 1:
The synchronization process is segmented into two distinct components: (1) transmission of compact message identification data, and (2) server-side message retrieval. This segmentation simplifies the mobile device's synchronization task to merely sending lightweight references, while the server handles the complex retrieval operations.
Solution Approach 2:
The server performs preliminary action by maintaining a complete local copy of sent messages and establishing a retrieval mechanism in advance. When the mobile device needs to resend a message, the server already has the full content ready to be retrieved using the transmitted message ID, eliminating the need for complex real-time synchronization.
3Loss of energy
If abbreviated reference ID is used for resending, then network bandwidth is conserved, but message synchronization must be well maintained
Solution Approach 1:
The system uses disposable, lightweight message identification references instead of persistent full message copies on the mobile device. These cheap reference objects contain only essential identification data, are easily transmitted, and can be discarded after use, while the server maintains the persistent full message copies.
Data Source
AI summary
An enhanced email system incorporating mobile wireless communication devices includes program logic for efficiently managing (i.e., at least partially synchronizing) “messages sent” files in the mobile device and in a related message server. The exemplary program logic also more efficiently handles resending of previously sent email messages from the mobile wireless communication device (especially in the context of synchronized messages sent files) by sending to the message server only abbreviated unique message ID in the first instance. In this way, wireless bandwidth is conserved as is the device battery.