Metadata-Based Email View Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional email viewing techniques provide a limited and static view of emails, failing to effectively leverage the diverse content types such as images, dates, and billing information, which restricts user interaction and organization of email content.

Innovation Solution

The implementation of metadata-based email viewing techniques that parse and combine content from multiple emails to provide dynamic and customizable views, allowing users to select representations of content types and aggregate views based on metadata, such as travel itineraries or receipts, enhancing user interface output.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional email viewing techniques are used, then the system is simple and easy to operate, but the view of email content is limited and static

Engineering Contradiction:
Improveview richnessVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments email content into distinct types (images, dates, billing information, etc.) using metadata tags, allowing the system to present different views based on content type without increasing overall system complexity. Each content type can be independently identified and displayed appropriately.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a metadata dimension to traditional email viewing, transforming static text-based emails into multi-dimensional content structures that include typed information, enabling rich views while maintaining the underlying simple email structure.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Ease of operation

If metadata-based content parsing is implemented, then content organization is improved, but processing time increases

Engineering Contradiction:
Improvecontent location efficiencyVSAvoidemail processing time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent applies metadata tagging and content type identification during email reception and storage, performing the organization work in advance rather than during user viewing. This preliminary processing enables rapid content location later without repeated parsing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces manual content scanning with automated metadata-based content identification, using structured data tags to quickly locate and present relevant information without requiring users to read through entire emails.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Loss of information

If multiple content types are aggregated from multiple emails, then information completeness is improved, but device complexity increases

Engineering Contradiction:
Improvecontent completenessVSAvoidemail management complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges content from multiple emails based on metadata associations (such as event-related emails), combining disparate information sources into a unified view that presents complete information without requiring users to manually correlate multiple messages.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces metadata as an intermediary layer that connects and relates content across multiple emails, enabling the system to automatically associate and aggregate relevant information without increasing user-facing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9836724B2Email views
Publication Date: 2017.12.05 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9836724B2 patent drawing
  • US9836724B2 patent drawing
  • US9836724B2 patent drawing

AI summary

Email viewing techniques are described. In implementations, a determination is made regarding one or more types of content that are included in an email through examination of metadata that describes the one or more types of content. The determination is made responsive to selection of an email in a user interface for output. A choice is made from one of a plurality of views for the email based on the determination; and the email is output in a user interface using the chosen view.