Application-Specific MIME Type for Cloud Storage Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud storage systems face challenges in securely granting access to user files while maintaining security, particularly when third-party applications need to open, create, or modify files stored by these services, which are organized by MIME types.

Innovation Solution

The system generates a unique application-specific MIME type for each third-party application, ensuring that only authorized applications can access and modify files by matching the application-specific ID with the ID extracted from the file, thereby enforcing security policies and preventing alteration of user data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If third-party applications are granted access to user files to enable opening, creating, or modifying operations, then application functionality and user convenience are improved, but security risks and potential unauthorized data alteration increase

Engineering Contradiction:
Improveapplication access capabilityVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments file access control by creating application-specific MIME types for each third-party application. Each application receives a unique MIME type identifier that acts as a digital signature, dividing the general file access permission into application-specific permission units. This allows the system to grant access to multiple applications while maintaining individualized security control for each application-file pair.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The application-specific MIME type serves as an intermediary mechanism between the application and the file system. Instead of directly granting access permissions, the system uses the MIME type as a mediating identifier that must match between the application and the file metadata. This intermediary layer enables secure access control by verifying identity through the MIME type match before allowing file operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If standardized MIME types are used for file organization, then file management efficiency is improved, but application-specific security control deteriorates

Engineering Contradiction:
Improvefile management efficiencyVSAvoidaccess control complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system applies local quality by maintaining standardized MIME types for general file categorization while adding application-specific quality markers to the MIME type string. The application-specific portion of the MIME type acts as a localized security attribute that provides fine-grained control for individual applications without disrupting the overall standardized file management structure. This allows different parts of the MIME type system to serve different purposes: the base type for organization and the suffix for security.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system changes the MIME type parameter structure by appending or prefixing application-specific identifiers to the standard MIME type string. This parameter modification transforms a generic file type identifier into a specific access control token. The transformation maintains compatibility with existing MIME type systems while adding the necessary security dimension through parameter extension.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9195840B2Application-specific file type generation and use
Publication Date: 2015.11.24 GOOGLE LLC
  • US9195840B2 patent drawing
  • US9195840B2 patent drawing
  • US9195840B2 patent drawing

AI summary

Techniques are described for facilitating file access control of a storage service. In response to a third-party application requesting access to a user's file, the service extracts an application-specific ID from a file type associated with the retrieved file; and grants access to the requested file in response to a determination that an application-specific ID for the third-party application matches an application-specific ID extracted from the file. This Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.