Email Client Permission-Protected Data Preview

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies for accessing protected content in cloud storage providers through email links are time-consuming and inefficient, requiring users to navigate away from the email client and enter login credentials, leading to increased resource usage and decreased interaction performance.

Innovation Solution

An email client system that receives a URL linked to protected content, determines the recipient's permissions, and renders a preview of the content within the email client interface, reducing the need for multiple application instances and credential entry by processing the content for a permission-protected preview.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the recipient clicks on the link to access protected content, then the content can be accessed, but the user is redirected away from the email client and required to enter login credentials, increasing time consumption and resource usage

Engineering Contradiction:
Improveease of accessing protected contentVSAvoidtime to access protected content
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by checking recipient permissions against the protected content before the user clicks the link. The email client pre-loads and caches the permission verification result, so when the user clicks the link, the authentication is already complete or expedited, eliminating the need for full login credential entry and reducing access time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The email client acts as an intermediary between the email server and the protected content storage service. It intercepts the link click event, handles the permission verification locally using pre-fetched credentials, and directly renders the content within the email client interface, bypassing the need for user redirection to external login pages

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If the recipient is redirected to the cloud storage provider to access the file, then the file can be accessed, but multiple application instances need to be opened, increasing resource usage

Engineering Contradiction:
Improveease of accessing fileVSAvoidcomputational resources for accessing content
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The system merges the email client functionality with the content rendering capability. Instead of opening separate applications for email and cloud storage access, the email client is enhanced to directly render protected content within its own interface, consolidating multiple functions into a single application instance and reducing overall system resource consumption

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The email client is transformed into a multi-functional application that not only handles email display and composition but also serves as a content viewer for protected files. By integrating the content rendering engine and permission verification system into the email client, it becomes a universal access point for both communication and file access, eliminating the need for separate cloud storage applications

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10749831B2Link with permission protected data preview
Publication Date: 2020.08.18 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10749831B2 patent drawing
  • US10749831B2 patent drawing
  • US10749831B2 patent drawing

AI summary

Aspects of the present disclosure relate to systems and methods for providing a preview of protected content in a user interface to an email client. An email client may receive an email message including a uniform resource locator (URL) linked to at least one item stored in a data service. The email client may send the URL to an email server to determine whether a recipient of the URL has permissions to the at least one item stored in the data service. When it is determined that the recipient of the URL has permissions to the at least one item stored in the data service, content for a permission protected preview of the at least one item may be received at the email client. The email client may render the permission protected preview of the at least one item in a user interface to the email client.