Email Draft Synchronization via Push Paradigm

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current synchronization systems for email drafts between host systems and handheld devices are manual, inefficient, and prone to delays, leading to bandwidth issues and increased user workload, as they rely on user-initiated actions and batch processing, which can result in missed updates and increased energy consumption.

Innovation Solution

Implementing a 'push' paradigm where email drafts are automatically synchronized in real-time or batched upon user-defined events, allowing continuous and efficient data replication between host and handheld devices, eliminating the need for user-initiated synchronization and reducing data transfer volumes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If batch-mode synchronization is used, then data replication between host system and handheld device is achieved, but synchronization delays occur and user workload increases

Engineering Contradiction:
Improvedata synchronization reliabilityVSAvoidsynchronization delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-synchronizing email drafts to the handheld device before the user needs them. The host system proactively pushes drafts to the device in advance, so when the user travels or needs access, the data is already available, eliminating synchronization delays and the need for manual pull actions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system establishes continuous synchronization through push-based mechanisms that maintain constant data flow between host and handheld device. Instead of periodic batch synchronization, the system continuously monitors and pushes updates as they occur, ensuring real-time consistency without user intervention and eliminating gaps where data might diverge.

Inventive Principle:
Principle #20Continuity of useful action

2Adaptability or versatility

If manual synchronization actions are required, then user control over data replication is maintained, but ease of operation deteriorates and user workload increases

Engineering Contradiction:
Improveuser control flexibilityVSAvoidsynchronization operation ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system implements self-service by automatically pushing email drafts from the host system to the handheld device without requiring user initiation. The synchronization process serves itself through automated event-driven mechanisms that detect when drafts are created or modified and automatically replicate them, eliminating manual user actions while maintaining data consistency.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback mechanisms to monitor the state of email drafts on both host and handheld devices. When changes are detected, the system receives feedback about the modification event and automatically triggers synchronization, creating a closed-loop system that adapts to user needs without requiring explicit commands while maintaining full data control.

Inventive Principle:
Principle #23Feedback

3Reliability

If frequent synchronization is performed, then data consistency between systems is improved, but energy consumption and bandwidth usage increase

Engineering Contradiction:
Improvedata consistencyVSAvoidhandheld device energy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system uses periodic action in a智能化的 way by triggering synchronization events based on specific conditions (when drafts are created, modified, or deleted) rather than continuous periodic polling. This event-driven approach maintains data consistency by synchronizing only when necessary, reducing unnecessary energy consumption and bandwidth usage while ensuring reliability.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system performs preliminary synchronization actions by pushing drafts to the handheld device in advance before they are needed. This proactive approach ensures data consistency is maintained without requiring continuous real-time synchronization, allowing the system to batch or delay transmissions optimally, thereby reducing energy consumption and bandwidth usage while maintaining reliability.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If large amounts of data are synchronized in batch mode, then complete data replication is achieved, but bandwidth efficiency deteriorates and transmission time increases

Engineering Contradiction:
Improvecomplete data replicationVSAvoiddata transmission efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system segments data synchronization by pushing individual email drafts or small groups of drafts separately rather than transmitting large batches at once. This segmentation allows for more efficient use of bandwidth, enables prioritization of critical data, and allows transmissions to occur during optimal network conditions, improving overall productivity while ensuring complete replication of all drafts through multiple smaller transmissions.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8566399B2Method and system for synchronizing a drafts folder
Publication Date: 2013.10.22 HUAWEI TECH CO LTD
  • US8566399B2 patent drawing
  • US8566399B2 patent drawing
  • US8566399B2 patent drawing

AI summary

A method and system for synchronizing a draft of an email is described. The system includes a computer device and a handheld device in communication with the computer device via a wireless communication network. The system further includes a saving module located in one or the other device to allow a user to save an email message therein as a draft. A sending module is located in the computer device (handheld device) for sending the draft therefrom to the handheld device (computer device). A send trigger module in the computer device (handheld device) issues instructions, which are unsolicited by the handheld device (computer device), that cause the sending module to send the draft from the computer device (handheld device) to the other device.