Email Metadata Routing for Non-Persistent Queue Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing email processing systems face inefficiencies due to reliance on persistent storage, which can lead to significant issues during system crashes and do not effectively manage message routing and load balancing, resulting in suboptimal performance and potential message loss.

Innovation Solution

The system employs non-persistent storage for message queues, utilizing metadata for routing and status information, and implements load balancing through dynamic queue management and message prioritization to ensure efficient processing and recovery from crashes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If persistent storage is used for message queues, then data reliability is improved, but I/O speed deteriorates

Engineering Contradiction:
Improvedata reliabilityVSAvoidI/O speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent segments message queue data into two parts: metadata (routing and status information) stored in non-persistent storage for fast access, and message content stored in persistent storage for reliability. This segmentation allows the system to achieve both fast I/O operations for queue management and data durability for message content.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces metadata as an intermediary layer between the message queue system and persistent storage. The metadata contains routing and status information that enables the system to manage queues efficiently in non-persistent storage while maintaining the ability to recover and reconstruct queue states without requiring persistent storage for every operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If non-persistent storage is used for message queues, then I/O speed is improved, but reliability deteriorates

Engineering Contradiction:
ImproveI/O speedVSAvoidreliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent performs preliminary actions by maintaining metadata that captures the essential state of message queues (routing information, status, etc.) in non-persistent storage. This metadata serves as a preliminary record that enables rapid queue operations while allowing the system to reconstruct full queue states from persistent storage if needed, thus achieving both speed and reliability.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If detailed message routing information is maintained, then message delivery accuracy is improved, but system complexity increases

Engineering Contradiction:
Improvemessage routing accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts routing and status information from the full message content and stores it separately as metadata in non-persistent storage. This extraction allows the system to maintain detailed routing information for accurate message delivery while keeping the main queue management operations simple and fast, as they only need to access the compact metadata rather than full message content.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS7698369B2Email delivery system using metadata on emails to manage virtual storage
Publication Date: 2010.04.13 MARIGOLD USA INC
  • US7698369B2 patent drawing
  • US7698369B2 patent drawing
  • US7698369B2 patent drawing

AI summary

E-mail system which organizes e-mails into queues based on their locations and characterizes the e-mails. Metadata, indicative of the e-mail, is appended to the e-mail. The queues are organized based on the metadata, and processed. The metadata is always stored in local storage; and the message body may be stored in local storage, or in remote storage, depending on how long it will be until the message is sent. A special server manages whether the information is stored in local or remote storage.