Mail Transport Agent Email Data Partitioning and Replay

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional email routing systems lack backup copies of email message data, leading to permanent loss if downstream recipient servers fail, as data is only briefly stored on mail transport agents and not locally retained.

Innovation Solution

Implementing a system where mail transport agents store email message data in a data store, partitioning it into time-based generations for efficient retrieval and backup, and periodically cleaning up expired data to maintain data contiguity and availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If email message data is only briefly stored on mail transport agents for routing purposes, then the routing efficiency is improved and storage resources are conserved, but data availability and reliability deteriorate causing permanent loss when downstream servers fail

Engineering Contradiction:
Improverouting efficiencyVSAvoiddata availability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary storage of email message data at the mail transport agent before downstream servers potentially fail. By storing data in advance in a data store with generations representing time frames, the system ensures data is available for replay if needed, resolving the contradiction between brief storage for efficiency and sufficient storage for reliability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates backup copies of email message data by storing generations of data in a data store. These copies enable replay functionality where lost data can be retrieved and retransmitted, maintaining reliability without requiring continuous brief storage that would impact routing efficiency

Inventive Principle:
Principle #26Copying

2Reliability

If backup copies of email message data are maintained and stored at mail transport agents, then data reliability and availability are improved, but storage resource consumption and system complexity increase

Engineering Contradiction:
Improvedata availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments email message data into generations where each generation represents a specific time frame. This segmentation organizes data chronologically, enabling efficient storage management, replay operations, and cleanup processes. The segmented structure reduces system complexity by providing clear boundaries and organization for backup data

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements periodic cleanup operations that remove expired generations from the data store based on predefined hold periods. This periodic action maintains data availability for backup purposes while automatically managing storage resources, reducing complexity by eliminating the need for manual intervention or continuous monitoring

Inventive Principle:
Principle #19Periodic action

3Quantity of substance

If the data store is continuously cleaned by removing expired generations, then storage space is freed and maintained, but data retrieval capability may be compromised if cleanup occurs before necessary replay

Engineering Contradiction:
Improvestorage spaceVSAvoiddata retrieval capability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system implements a feedback mechanism where cleanup operations monitor and respond to replay requests. When a downstream server requests replay of messaging data, the system detects this need and adjusts cleanup operations accordingly, suspending deletion of generations that contain unprocessed or requested data. This feedback loop ensures storage space is freed while maintaining data retrieval capability

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary checks before deleting generations to ensure no replay operations are pending or needed. By checking for unprocessed email messages and replay requests before cleanup, the system prevents premature deletion that would compromise data retrieval, while still enabling regular cleanup to maintain storage space

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8805942B2Storing and partitioning email messaging data
Publication Date: 2014.08.12 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8805942B2 patent drawing
  • US8805942B2 patent drawing
  • US8805942B2 patent drawing

AI summary

A system is provided for storing messaging data at a mail transport agent in a network environment. An email message may be transmitted over a network from a sender client to a recipient server through a plurality of mail transport agents (MTA). An MTA may receive an email message and may store messaging data for the email message in a data store associated with the MTA. The MTA may partition the messaging data into generations representing a defined time frame for the date and time that an email message was received. The MTA may enable a search operation to be performed on the stored generations for retrieving and replaying messaging data to a downstream recipient server. The MTA may continually clean the data store by deleting from the data store a generation of data that has expired and outlived the predefined hold period.