Recipient-Specific Access Codes for Secure File Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for sharing items, such as files, lack a comprehensive solution that ensures secure, convenient, and efficient distribution and management of access permissions among users, particularly in collaborative environments.

Innovation Solution

A collaboration system that generates unique recipient-specific codes for accessing shared items, allowing secure access and management of permissions through Email messages, with features like secure access keys, version control, and audit tracking.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional Email sharing is used, then simplicity and ease of operation are maintained, but security and access control are insufficient

Engineering Contradiction:
Improveease of sharingVSAvoidaccess security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the access control mechanism by generating unique recipient-specific codes for each recipient instead of using a single shared access key. This segmentation allows the system to maintain the simplicity of Email sharing while implementing secure, individualized access control for each recipient.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If manual forwarding of updated items is used, then simplicity is maintained, but time consumption and productivity are reduced

Engineering Contradiction:
ImprovesimplicityVSAvoidupdate distribution efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent implements a feedback mechanism where the collaboration system automatically detects changes to shared items and pushes updated versions to all recipients. This eliminates the need for manual forwarding of updates, significantly improving productivity while maintaining operational simplicity through automated processes.

Inventive Principle:
Principle #23Feedback

3Reliability

If centralized file sharing functionality is used, then access control and security are improved, but device complexity and ease of operation deteriorate

Engineering Contradiction:
Improveaccess controlVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a collaboration system as an intermediary layer between Email and file sharing functionality. This intermediary handles the complex access control, authentication, and update distribution mechanisms, allowing users to maintain simple Email-based interaction while benefiting from secure, controlled file sharing capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If recipient-specific codes are generated for each recipient, then access security and control are improved, but system complexity increases

Engineering Contradiction:
Improveaccess controlVSAvoidcode management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service functionality where the collaboration system automatically generates, manages, and distributes recipient-specific codes without requiring manual intervention. The system handles code generation, storage, and distribution autonomously, improving access control while minimizing the operational complexity for users.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8930469B2Functionality for sharing items using recipient-specific access codes
Publication Date: 2015.01.06 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8930469B2 patent drawing
  • US8930469B2 patent drawing
  • US8930469B2 patent drawing

AI summary

A collaboration system is described for sharing files. The collaboration system operates by receiving an Email message from a sender, the Email message specifying an attachment item (such as a file) and one or more recipients. The Email message also specifies a sender code assigned to the sender for the particular attachment item. The collaboration system stores the attachment item and then generates a recipient-specific code associated with each recipient who is to receive the Email message. The collaboration system then sends a recipient-tailored Email message to each recipient. Each recipient-tailored Email message contains Email content provided by the original Email message along with a recipient-specific code associated with the recipient. Each recipient can access the attachment item via its recipient-specific code, which constitutes a secure access key.