Email File Delivery via Placeholder and Background Upload

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional email file attachment delivery methods are inefficient, particularly for large files, leading to significant productivity losses and infrastructure strain due to lengthy attachment processes, data loss, latency, and inadequate management of sensitive files, which necessitate a solution that supports existing workflows and enhances collaboration.

Innovation Solution

An email distribution system that uses a hosting server to manage large file attachments by inserting placeholders in emails, allowing background processing and transfer, enabling seamless delivery and lifecycle management while maintaining user productivity and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If large files are attached to emails using conventional methods, then file delivery capability is improved, but attachment time and email client tie-up time increase significantly

Engineering Contradiction:
Improvefile sizeVSAvoidattachment time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The system performs preliminary actions by separating the file upload process from the email sending process. The placeholder is inserted into the email immediately, while the actual file upload occurs in the background before the email is sent. This allows the email client to return control to the user quickly without waiting for the entire file upload to complete.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The attachment process is segmented into distinct phases: (1) inserting a placeholder into the email, (2) uploading the file in the background to a hosting server, and (3) sending the email with the placeholder. This segmentation allows the email client to handle only the lightweight placeholder operation while the heavy file upload occurs separately in the background.

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If large files are attached to emails using conventional methods, then file delivery capability is improved, but email client performance and availability are degraded

Engineering Contradiction:
Improvefile sizeVSAvoidemail client availability
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The system performs preliminary actions by separating the file upload process from the email sending process. The placeholder is inserted into the email immediately, while the actual file upload occurs in the background before the email is sent. This allows the email client to return control to the user quickly without waiting for the entire file upload to complete.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A hosting server acts as an intermediary between the email client and the final destination. The file is uploaded to this intermediate hosting server in the background, allowing the email client to remain responsive and available while the heavy file transfer operation completes separately.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If existing email infrastructure is used for large file attachments, then system simplicity is maintained, but network bandwidth and storage resources are strained

Engineering Contradiction:
Improvesystem complexityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Device complexityVSLoss of energy

Solution Approach 1:

A hosting server acts as an intermediary between the email client and the final destination. The file is uploaded to this intermediate hosting server in the background, allowing the email client to remain responsive and available while the heavy file transfer operation completes separately.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the file upload function from the traditional email transmission path. Instead of routing large files through the email server infrastructure, files are uploaded separately to a hosting server, removing the bandwidth and storage burden from the email system while maintaining system simplicity.

Inventive Principle:
Principle #2Taking out (Extraction)

4Ease of operation

If conventional email attachment methods are used, then workflow simplicity is maintained, but data loss and latency issues occur

Engineering Contradiction:
Improveworkflow simplicityVSAvoiddata delivery reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary actions by separating the file upload process from the email sending process. The placeholder is inserted into the email immediately, while the actual file upload occurs in the background before the email is sent. This allows the email client to return control to the user quickly without waiting for the entire file upload to complete.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A hosting server acts as an intermediary between the email client and the final destination. The file is uploaded to this intermediate hosting server in the background, allowing the email client to remain responsive and available while the heavy file transfer operation completes separately.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9503280B2Methods and systems for email integrated file delivery
Publication Date: 2016.11.22 KITEWORKS USA LLC
  • US9503280B2 patent drawing
  • US9503280B2 patent drawing
  • US9503280B2 patent drawing

AI summary

Methods and systems consistent with the present invention provide a file delivery system for transmitting files to recipients using email, which may be used with existing email infrastructure. Email clients may “attach” files to an email by an attachment process. The attachment process, however, associates a placeholder with the email instead of the actual file. The placeholder is replaced with a URL link to the file and the email is sent. The system moves the attachments over the network to a remote server that is capable of delivering the attachments to the email recipients. File attachments are routed to recipients independent of the associated email.