Email Routing Control via Latency Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current email systems lack efficient mechanisms to identify and mitigate latency issues, such as choke points, in email message routing, which can lead to delayed message delivery and poor performance.

Innovation Solution

An email computing system architecture that aggregates route information and per-hop latency data to identify choke points, generating control signals to reroute email messages and communicate with service providers to address latency issues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If email messages are routed through multiple servers, then delivery reliability is improved, but latency increases due to choke points

Engineering Contradiction:
Improveemail delivery reliabilityVSAvoidemail delivery latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system dynamically adjusts routing paths based on real-time latency monitoring and choke point detection. When a choke point is identified, the system automatically reroutes email messages through alternative server paths, making the routing flexible and adaptive rather than static.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements continuous feedback loops by monitoring per-hop latency and identifying choke points. This feedback information is used to generate control signals that modify routing decisions, creating a closed-loop control system that optimizes delivery performance.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If per-hop latency monitoring is implemented, then latency identification capability is improved, but system complexity increases

Engineering Contradiction:
Improvelatency measurement precisionVSAvoidmonitoring system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system performs self-diagnosis by automatically monitoring its own latency performance and identifying choke points without external intervention. Each server in the routing path contributes latency data, and the system autonomously processes this information to detect performance issues.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The monitoring system divides the email routing path into discrete hops between servers, measuring latency for each segment individually. This segmentation allows precise identification of where latency occurs without requiring complex end-to-end analysis.

Inventive Principle:
Principle #1Segmentation

3Productivity

If choke point identification is automated, then mitigation speed is improved, but control system complexity increases

Engineering Contradiction:
Improvemitigation speedVSAvoidcontrol system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system pre-establishes alternative routing paths and control signals before choke points are actually encountered. When latency issues are detected, the system can immediately activate pre-planned mitigation strategies, reducing response time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary control mechanism that sits between latency monitoring and routing decisions. This intermediary processes latency data, identifies choke points, and generates appropriate control signals, separating the complexity of analysis from the simplicity of execution.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10680933B2Electronic mail system routing control
Publication Date: 2020.06.09 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10680933B2 patent drawing
  • US10680933B2 patent drawing
  • US10680933B2 patent drawing

AI summary

Route information identifying servers that an e-mail message travels through, along with per-hop latency information, is aggregated. A choke point or other latency-related issue is identified and a control signal is generated to control the e-mail system based upon the identified choke point or other latency-related issue.